I found a framework that is supposed to be multi-threaded (https://aqueduct.io/) and did a simple test with it and it is a bit better (my results with the same test as in here were ~200k req/s for go and ~10k req/s for the implementation here, and ~35k req/s for aqueduct with 4 threads too). Another catch is dart can be compiled to native code or run a VM, but not all packages work compiled as native code, and this aqueduct framework uses one of them so I had to do the test in the VM.

Because of this I tried (very hard) to do a simple implementation using a pool of Isolates (threads) with plain dart but failed, mainly because isolate can only communicate via messages that can only be of primitive types (int, String, etc.), so I can’t really reply to requests in other threads.

I was really interested in knowing how dart performance compares to go, and this was an interesting example. It’s a bit sad to realize that dart isn’t even capable to offer a multi-threading flexible enough to implement a decent web server…