Am Sonntag, 16. November 2008 21:04:25 schrieb vicente.botet:

----- Original Message ----- From: <k-oli@gmx.de> To: <boost@lists.boost.org> Sent: Sunday, November 16, 2008 5:20 PM Subject: [boost] [threadpool] new version 16: pining of processors(processor affinity)

...

Hello,

I've uploaded a new version (16) to boost vault. In the new version as much worker-threads are created as boost::thread::hardware_concurrency() returns if no poolsize is specified in the pool constructor . Each worker-thread will be pined to one processor.

Have you get some performance improvements?

Yes - internaly a work-stealing algorithm is used and thatswhy pining threads to processors improves the performance. Oliver

k-oli@gmx.de wrote:

...

Yes - internaly a work-stealing algorithm is used and thatswhy pining threads to processors improves the performance.

Couldn't it also be inefficient for some patterns?

You are not frced to used the pining. If you specify poolsize in the cosntructor no pining will happen. Boost.Threadpool uses internaly a work-stealing algorithm. Each worker-thread has its own local queue (containing tasks) which will be filled by sub-tasks (please see the docu). The idea is that memory associated with the work most recently pushed into the queue will still be hot in the cache (queue == Processor affinity is optimizing cache performance (even time-sensitive applications). Oliver -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer