Comment on A Solution to CPU-intensive Tasks in IO LoopsparentComments−yxhuvud14yWhat are your thoughts on the disruptor pattern? It seems to me to be something that tries to eat the cake of multithreading while still having a lot of the simplicity of eventing.( https://code.google.com/p/disruptor/ )−willvarfar14yIts a very different approach. I do like their presentations and I've really got a thing for the "mechanical sympathy" term they coined.At a glance I'd say its not really the solving the same problems and isn't generally applicable to, say, application web servers.I would love to be educated on that score ;)−jamii14yThe disruptor is just a very efficient event loop. It doesn't prevent you from blocking the handling thread.−yxhuvud14yTrue, if you do blocking stuff in the handler instead of in the worker threads.
Comments
What are your thoughts on the disruptor pattern? It seems to me to be something that tries to eat the cake of multithreading while still having a lot of the simplicity of eventing.
( https://code.google.com/p/disruptor/ )
Its a very different approach. I do like their presentations and I've really got a thing for the "mechanical sympathy" term they coined.
At a glance I'd say its not really the solving the same problems and isn't generally applicable to, say, application web servers.
I would love to be educated on that score ;)
The disruptor is just a very efficient event loop. It doesn't prevent you from blocking the handling thread.
True, if you do blocking stuff in the handler instead of in the worker threads.