Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # dev >> KAFKA-50 replication support and the Disruptor


Copy link to this message
-
Re: KAFKA-50 replication support and the Disruptor
On 10/31/2011 04:23 AM, Erik van Oosten wrote:
> That is not the point (mostly). While you're waiting for a lock, you can't issue another IO request. Avoiding locking is worthwhile even if CPU is the bottleneck. The advantage is that you'll get lower latency and also important, less jitter.

/begin{Tangent}

Doesn't the Disruptor use a spin lock though?  I would expect that to
not play nice if sharing a core with CPU bound threads doing 'real' work.