# Fun with my-Channels Nirvana and Azul Zing

DevFeed: [Fun with my-Channels Nirvana and Azul Zing](<https://devfeed.tech/articles/fun-with-my-channels-nirvana-and-azul-zing-13623.md>)

Original publisher: [Read original article](<https://mechanical-sympathy.blogspot.com/2012/03/fun-with-my-channels-nirvana-and-azul.html>)

Author: Martin Thompson (noreply@blogger.com)

Published: 2012-03-22T17:55:00Z

Content type: article

Language: en

Sources: [Mechanical Sympathy](<https://devfeed.tech/sources/mechanical-sympathy.md>)

Topics: [Low Latency](<https://devfeed.tech/topics/low-latency.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Java](<https://devfeed.tech/topics/java.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [ipc](<https://devfeed.tech/tags/ipc.md>), [java](<https://devfeed.tech/tags/java.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [messaging](<https://devfeed.tech/tags/messaging.md>)

## AI overview

An engineering article examines my-Channels' low-latency messaging system under load. Profiling identified lock contention as the main limit on latency and throughput; replacing the standard Java executor with a lock-free executor produced tests showing about 10x better performance and enabled 16x more throughput.

## Source excerpt

Since leaving LMAX I have been neglecting my blog a bit. This is not because I have not been doing anything interesting. Quite the opposite really, things have been so busy the blog has taken a back seat. I've been consulting for a number of hedge funds and product companies, most of which are super secretive. One company I have been spending quite a bit of time with is my-Channels, a messaging provider. They are really cool and have given me their blessing to blog about some of the interesting things I've been working on for them. For context, my-Channels are a messaging provider that specialise in delivering data to every device known to man over dodgy networks such as the Internet or your corporate WAN. They can deliver live financial market data to your desktop, laptop at home, or your iPhone, at the fastest possible rates. Lately, they have made the strategic move to enter the low-latency messaging space for the enterprise, and as part of this they have enlisted my services. They want to go low-latency without giving up the rich functionality their product offers which is giving me some interesting challenges. Just how bad is the latency of such a product when new to the low-latency space? I did not have high expectations because to be fair this was never their goal. After some initial tests, I'm thinking these guys are not in bad shape. They beat the crap out of most JMS implementations and it is going to be fun pushing them to the serious end of the low-latency space. OK enough of the basic tests, now it is time to get serious. I worked with them to create appropriate load tests and get the profilers running. No big surprises here, when we piled on the pressure, lock-contention came out as the biggest culprit limiting both latency and throughput. As we go down the list, lots of other interesting things showed up but let's follow good discipline and start at the top of the list. Good discipline for "Theory of Constraints" states that you always work on the mos