<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NIO on Bit Mojo – Hiram Chirino</title><link>https://hiramchirino.com/tags/nio/</link><description>Recent content in NIO on Bit Mojo – Hiram Chirino</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 26 Jul 2010 11:28:50 +0000</lastBuildDate><atom:link href="https://hiramchirino.com/tags/nio/index.xml" rel="self" type="application/rss+xml"/><item><title>HawtDispatch Event Based IO</title><link>https://hiramchirino.com/2010/07/26/hawtdispatch-event-based-io/</link><pubDate>Mon, 26 Jul 2010 11:28:50 +0000</pubDate><guid>https://hiramchirino.com/2010/07/26/hawtdispatch-event-based-io/</guid><description>My previous post promised a follow up to explain how network IO events are handled by HawtDispatch. Before I get into the details, I urge you to read Mark McGranaghan&amp;rsquo;s post on Threaded vs Evented Servers. He does an excellent job describing how event driven servers scale in comparison to threaded servers. This post will try to highlight how HawtDispatch provides an excellent framework for the implementation of event based servers.</description></item><item><title>Scaling Up with HawtDispatch</title><link>https://hiramchirino.com/2010/06/03/scaling-up-with-hawtdispatch/</link><pubDate>Thu, 03 Jun 2010 11:04:08 +0000</pubDate><guid>https://hiramchirino.com/2010/06/03/scaling-up-with-hawtdispatch/</guid><description>I just spotted an excellent article on how reducing the number of cores used by a multi-threaded actually increased it&amp;rsquo;s performance. This seems counter intuitive at first, but it is a sad reality. It is very easy to create contention across threads in a multi-threaded app which in turn lowers performance.
A few months ago, I experienced similar results while hacking on ActiveMQ. I noticed that passing messages from producer connections to consumer connections was dramatically faster if the producer and consumer were being serviced by the same thread.</description></item></channel></rss>