3 ms·
I was referring to the fact that it is the only async implementation that I know of that compiles to a state machine that doesn't need to allocate new memory fo
by xiphias2 7y ago
I was referring to the fact that it is the only async implementation that I know of that compiles to a state machine that doesn't need to allocate new memory for each continuation. I think it will translate to extremely fast web services in practice.
Pinning is of course part of the elegant solution. There are some great videos about it:
https://www.youtube.com/watch?v=lJ3NC-R3gSI&t=1710s https://www.youtube.com/watch?v=lJ3NC-R3gSI&t=1710s
https://www.youtube.com/watch?v=skos4B5x7qE https://www.youtube.com/watch?v=skos4B5x7qE
- majewsky 7y ago> I think it will translate to extremely fast web services in practice. In practice, it's probably not going to matter all that much because the average web service does way more time-expensive things like disk IO or SQL queries. The more significant effect is that async-await being really really fast enables you to use it in more places. For example, if you have a tight computation loop where different aspects of the logic are meshed together in a hard-to-read way, now you could try detangling it into several async actors talking to each other to make it more readable, without utterly destroying the performance characteristics.