5 ms·

You haven't written a concurrent Go program. Not sure what you're trying to demonstrate.

• cyberax 3y ago
  Yes. Because that's the point. I'm comparing overhead of async calls vs. normal calls.
  • schemescape 3y ago
    Note that you’re changing multiple variables, namely the entire compiler and runtime.
    • cyberax 3y ago
      If you know a system that both has async/await _and_ full-blown green threads, then I can try to test it.
      • gpderetta 3y ago
        C++ has now both async (built-in) and multiple flavors of stackful coroutines (as external libraries). You can run both on top of ASIO so that you can measure purely difference of the coroutine implementation as opposed to the runtime.
      • michaelsbradley 3y ago
        Racket has full-blown green threads (virtual threads)[1] that serve as an alternative to the async/await paradigm. It also supports use of native (OS) threads[2]. [1] https://docs.racket-lang.org/reference/eval-model.html#%28part._thread-model%29 https://docs.racket-lang.org/reference/eval-model.html#%28pa... [2] https://docs.racket-lang.org/reference/places.html https://docs.racket-lang.org/reference/places.html [&] https://docs.racket-lang.org/reference/futures.html https://docs.racket-lang.org/reference/futures.html