Re: Boolean Thread::Semaphore ?

Why not use a Thread::Queue to distribute the work to your worker threads? The workers will block when the queue is empty and get woken up when there is work to be done.

Comment on Re: Boolean Thread::Semaphore ?

Replies are listed 'Best First'.
Re^2: Boolean Thread::Semaphore ? by chrestomanci (Priest) on Feb 08, 2012 at 12:12 UTC
I am doing that, the work finding thread is putting the work it finds into a Thread::Queue object. The reason I want to use a semaphore as well is because the work finder runs much faster than the workers, but is quite expensive in terms of resource consumption. If there was not a mechanism to pause the work finder when there is enough work in the queue, it would build a queue of millions of items and waste a lot of memory and other resources in the process.	[reply]

Replies are listed 'Best First'.

Re^2: Boolean Thread::Semaphore ?
by chrestomanci (Priest) on Feb 08, 2012 at 12:12 UTC

I am doing that, the work finding thread is putting the work it finds into a Thread::Queue object.

The reason I want to use a semaphore as well is because the work finder runs much faster than the workers, but is quite expensive in terms of resource consumption.

If there was not a mechanism to pause the work finder when there is enough work in the queue, it would build a queue of millions of items and waste a lot of memory and other resources in the process.

[reply]