What thread / isolate does flutter run IO operations on?

Question

In flutter when using the http package or doing general IO operations for example

import 'package:http/http.dart' as http;

http.Response response = await http.get(url);
if (response.statusCode == 200) {
  var json = jsonDecode(response.body); 
}

I have read through The engine architecture which indicates there are 4 threads in the engine

• Platform Task Runner
• UI Task Runner
• GPU Task Runner
• IO Task Runner

The main app dart code runs on the UI Task Runner Thread. The IO task runner seems to be only for the dart engine to read images handle time consuming image IO and not where application IO happens?

I understand that the IO libraries have no-blocking Future based interfaces so the callbacks I provide to the IO libraries will run on the UI thread but what about the actual IO operations themselves is there an OS thread that the Dart VM is using to do these operations?

For example if I try to upload/download an 800MB video file is there a background IO thread that the Dart VM uses do the actual IO?

Should a separate isolate be used for large IO operations like uploading / downloading large files?

Answer 1

Dart handles IO requests with a thread pool. To find out I had to clone the Dart SDK and look into the source code, as I couldn't find answer from the docs.

When an IO method is called, the File implementation _File class method is called. It creates a Port to native code (IOService_NewServicePort) and sends the IO request id and args to native code. The native code handles the IO requests with a thread pool (runtime\vm\native_api_impl.cc#Dart_NewNativePort), submiting a task into the thread pool. Then the native code returns all the way back to Dart code and _File returns a future object. After the IO operation is done, the result is sent back from native to Dart by the port created before. This triggers a handler registered on the port and the future is resolved.