From Java docs for `jdk.virtualThreadScheduler.maxPoolSize`: the default is 256. So yeah I can see that starving rather quickly, particularly with benchmarking

From Java docs for `jdk.virtualThreadScheduler.maxPoolSize`: the default is 256. So yeah I can see that starving rather quickly, particularly with benchmarking-like workloads. Synchronized is very very common, 256 concurrent calls really doesn't seem all that abnormal. If that were raised to like max-int32 would things be fine, semantically? That'd mimic real threads limits (no jvm limit at all afaict).