Message Passing, Performance - Take 2

Oren Eini

Jul. 16, 14 · Interview

Likes (0)

Comment

Save

5.2K Views

In my previous post, I did some rough “benchmarks” to see how message passing options behave. I got some great comments, and I thought I’ll expand on that.

The baseline for this was a blocking queue, and we managed to process using that we managed to get:

145,271,000 msgs in 00:00:10.4597977 for 13,888,510 ops/sec

And the async BufferBlock, using which we got:

43,268,149 msgs in 00:00:10 for 4,326,815 ops/sec.

Using LMAX Disruptor we got a disappointing:

29,791,996 msgs in 00:00:10.0003334 for 2,979,100 ops/sec

However, it was pointed out that I can significantly improve this if I changed the code to be:

var disruptor = new Disruptor.Dsl.Disruptor<Holder>(() => new Holder(), new SingleThreadedClaimStrategy(256), new YieldingWaitStrategy(), TaskScheduler.Default);

After which we get a very nice:

141,501,999 msgs in 00:00:10.0000051 for 14,150,193 ops/sec

Another request I got was for testing this with a concurrent queue, which is actually what it is meant to do. The code is actually the same as the blocking queue, we just changed Bus<string> to ConcurrentQueue<string>.

Using that, we got:

170,726,000 msgs in 00:00:10.0000042 for 17,072,593 ops/sec

And yes, this is pretty much just because I could. Any of those methods is quite significantly higher than anything close to what I actually need.

Message passing

Published at DZone with permission of Oren Eini. See the original article here.

Opinions expressed by DZone contributors are their own.

Trending

Message Passing, Performance - Take 2

Partner Resources