they are still more expensive than compiled async await, also mixing compute and... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		tcfhgj 14 hours ago \| parent \| context \| favorite \| on: A Design Space Exploration of Async/Await they are still more expensive than compiled async await, also mixing compute and io-bound work can cause issues
		help

mitxela 13 hours ago [–]

How sure are you? Got a benchmark?

tcfhgj 11 hours ago | [–]

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)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact