ring

hawari 2018-03-02T03:30:50.000108Z

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)?

seancorfield 2018-03-02T05:43:58.000053Z

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

hawari 2018-03-02T08:12:33.000200Z

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.

mpenet 2018-03-02T09:07:42.000370Z

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"

mpenet 2018-03-02T09:09:12.000156Z

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

hawari 2018-03-02T10:42:13.000266Z

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