Question

I am designing a new improved Logger component (.NET 3.5, C#).

I would like to use a lock-free implementation.

Logging events will be sent from (potentially) multiple threads, although only a single thread will do the actual output to file/other storage medium.

In essence, all the writers are * enqueuing* their data into some queue, to be retrieves by some other process (LogFileWriter).

Can this be achieved in a lock-less manner? i could not find a direct reference to this particular problem on the net.

Answer 1

If you find that using a lock in this case is too slow, you have a much bigger problem. A lock, when it’s not contended, takes about 75 nanoseconds on my system (2.0 GHz Core 2 Quad). When it’s contended, of course, it’s going to take somewhat longer. But since the lock is just protecting a call to Enqueue or Dequeue, it’s unlikely that the total time for a log write will be much more than that 75 nanoseconds.

If the lock is a problem–that is, if you find your threads lining up behind that lock and causing noticeable slowdowns in your application–then it’s unlikely that making a lock-free queue is going to help much. Why? Because if you’re really writing that much to the log, your lock-free blocking queue is going to fill up so fast you’ll be limited to the speed of the I/O subsystem.

I have a multi-threaded application that writes on the order of 200 log entries a second to a Queue<string> that’s protected by a simple lock. I’ve never noticed any significant lock contention, and processing isn’t slowed in the least bit. That 75 ns is dwarfed by the time it takes to do everything else.