Comment on A Design Space Exploration of Async/AwaitparentComments−tcfhgj7hthey are still more expensive than compiled async await, also mixing compute and io-bound work can cause issues−mitxela6hHow sure are you? Got a benchmark?−tcfhgj4h100% sure - Java just has to store and process more than a simple state machine, also if all threads are busy with compute bound work, async work is stalled if you don't put the compute bound work on adedicated thread (pool)
Comments
they are still more expensive than compiled async await, also mixing compute and io-bound work can cause issues
How sure are you? Got a benchmark?
100% sure - Java just has to store and process more than a simple state machine, also if all threads are busy with compute bound work, async work is stalled if you don't put the compute bound work on adedicated thread (pool)