Fork me on GitHub
#ring
<
2018-03-02
>
hawari03:03:50

With that being said @weavejester, if performance and efficiency are something of high importance, then is asynchronous handler is the absolute way to go? Or is it not a silver bullet in terms of performance (e.g. in some cases it could hinder performance instead)?

seancorfield05:03:58

My first reaction to that is "nothing is a silver bullet" 🙂 Everything is trade offs...

hawari08:03:33

Yeah, that is as expected, but I'd like to be more informed on what is the trade off on using async handlers beside the complexity it introduces.

mpenet09:03:42

If you handler does "slow" IO (and has an async interface) async would be more efficient, if not that's a bit useless, ex: for a simple "fast" handler the cost of context switching might cost you more if you use async. async handlers also come with a cost in complexity. So yeah the answer is "it depends"

mpenet09:03:12

in general, I would say don't bother with async at the beginning

hawari10:03:13

Thank you @mpenet for clarifying, I was contemplating to use async but unsure whether the benefit will outweigh the effort.