happymorning

• About: I know some tips & tricks for informatics

Recent Actions

• Commented on A plan for revamping and replacing the Perl debugger.
  You may check Devel::ebug ; it's a module that provide a clean API over the perl debugger....
• Commented on Thread pool for a boss/worker model
  I can propose a very different way using zeroMQ . It a powerful yet simple library for messaging between processes, you may implements everything you need just using simples processes communicating easily with each others. Using only messaging, you drop...

Comment Threads

• rhesa commented on Thread pool for a boss/worker model

  Another suggestion: beanstalkd and the Perl module Beanstalk::Client.

  I use this by forking off a number of workers per machine. Then I add more machines as load increases. Having isolated processes that only talk to the beanstalkd server means I don't have to deal with synchronisation or blocking issues. This makes for very simple and efficient code.

• Kal commented on Thread pool for a boss/worker model

  beanstalk seems to be very much like Gearman. Its a TCP client/server model in which you feed jobs into 'tubes' or queues on the server, and workers which join to the server and then consume those jobs. You can't register capabilities, but I'm assuming you could have differently capable workers pulling jobs from different tubes. This looks like a more simple API than Gearman, but the source for Gearman is easier to read - the beanstalk client source looks - err.. optimized, but I'd have to benchmark to see if it makes any difference. :)

  The problem with these for my application lies …

• chimerix commented on Thread pool for a boss/worker model

  Have you seen Parallel::Workers or Thread::Pool on CPAN?

• renodino commented on Thread pool for a boss/worker model

  Gratuitous self promotion: Thread::Apartment provides a pooling interface, and should allow use of direct method calls to threaded objects.

• Ron Savage commented on Thread pool for a boss/worker model

  Hi Kal

  Beanstalk::Client is written by Graham Barr, which is a big plus in my books.

  BTW: I haven't used any of these, but would be v-e-r-y confused if confronted with the need to to do.

  As for overlooking those modules I listed, I'm not surprised. Many modules have obscurantistic names.

  That's why I keep a tiddlywiki (check them out!) (one of many) for Perl with a section dedicated to 'Interesting Modules' I stumble across.

  I guess it's time to calve out that list into its own web page and put it on my site. I'll do that over the next week and blog on…