Did you try https://gist.github.com/huxi/81c152a672d1b39aed64 with different delays? (If you find anything wrong with that code, please let me know.)
The output on my system with 0ms, 1ms and 10ms delays looks like this: http://pastebin.com/za07QmUU Unfairness increases with the amount of time a lock is held. This isn’t a theoretical phantom issue, either. It bit us in production. So if locking is used, it is important to keep that in mind. I simply wanted to raise awareness about it. Not using locking at all would definitely be ideal. I need to take a closer look at org.apache.logging.log4j.core.async.AsyncLogger and Disruptor in general. Joern. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
