The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.
 / 
Thread-Conveyor-0.10
River stage one • 2 direct dependents • 3 total dependents
++

Changes for version 0.10

  • Replaced dependency on Thread::Serialize by dependency on Thread::Tie as the default, memory optimized implementation, now uses Thread::Tie.
  • Changed Thread::Conveyor so that it uses T::C::Tied for unthrottled belts when optimizing for memory.
  • Changed T::C::Throttled so that it makes its own decision on which belt implementation to be used, either T::C::Array (optimized for CPU) or T::C::Tied (optimized for memory).
  • Added "semaphore" object method to T::C::Array for obtaining the lock() semaphore, needed by T::C::Throttled.
  • Removed T::C::Thread from the distribution. This shaves about 1200 bytes off of the distribution package.
  • Replaced Thread::Conveyor::Thread by Thread::Conveyor::Tied, which uses Thread::Tie as its shared array implementation. This has the side-effect to being almost twice as slow but saving 18% of memory (at least in the test-suite). So there is now a true CPU versus memory trade-off. Main difference in CPU is caused by the fact that whole array fetches aren't possible using the tie() interface (this is a loop with FETCH()), wherease T::C::Thread was optimized to deal with that case). Main difference in memory is caused by the fact that only one thread (the Thread::Tie default thread) is used for all belts, whereas before each belt had its own thread. So the savings in memory could in real world situations, be quite a lot more than the 18% seen in the test-suite.

Modules

Thread::Conveyor
transport of any data-structure between threads
Thread::Conveyor::Array
array implementation of Thread::Conveyor
Thread::Conveyor::Throttled
helper class of Thread::Conveyor
Thread::Conveyor::Tied
tied array implementation of Thread::Conveyor

Other files