A simple benchmark comparing java loom virtual thread and kotlin coroutines

This page summarizes the projects mentioned and recommended in the original post on /r/Kotlin

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • go

    The Go programming language

    Have seen many discussions comparing them but didn't really see any benchmark numbers, so I decide to do a simple benchmark with the same 'concurrent prime sieve' algorithm golang uses on its \[homepage\]([https://golang.org/](https://golang.org/)) to demonstrate its goroutine performance. The [result]([https://programming-language-benchmarks.vercel.app/problem/prime-sieve](https://programming-language-benchmarks.vercel.app/problem/prime-sieve) shows kotlin coroutines (on JVM16) is \~2.5x slower than go(1.16.3), while java loom(ea jdk build 17-loom+6-225) is \~4.5x slower. The result is a little surprising to me, loom is not as performant as I was expecting. :(

  • jmh

    https://openjdk.org/projects/code-tools/jmh

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  • jdk7u-jdk

    SynchronousQueue is literally using the implementations you describe. Are you confusing this with another structure, like LinkedBlockingQueue?

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts