lmax - Maximum number of disruptors in an application -


using lmax disruptor,we have observed if use 5-10 disruptors in application (sort of chain of disruptors every disruptor having 1 consumer on performing specified task , handing on message next disruptor/ ringbuffer), happens cpu utilization reaches 90% , above , system becomes unresponsive until bring down application, feel it's because of many active disruptor threads. happens when disruptors not processing anything. can comment on should optimum number of disruptors used in application?

it need change wait strategies using on consumers. if using busy-wait strategy on of them, if no inputs have been provided ring buffers, polling threads still tie cpu resources because they'll in tight loops they're checking buffer new values read.


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -