[tpm] Single thread Perl 5.8.8 vs. Multi-threaded Perl 5.10.1

Shane Boyce Shane.Boyce at gennum.com
Fri Nov 20 12:27:12 PST 2009

Hi J. Bobby,

My company uses Perl scripts to upload ASCII text data files into Oracle. The uploads happen on a system that can handle up to 32 threads. So multi-threading is still of massive time benefit even though we had to have numerous threads to overcome the initial decrease in performance from single to multi-threaded Perl. The uploaders currently run with up to 12 threads as the benchmark study showed that more than that had very diminished returns for our system setup.


From: J. Bobby Lopez [mailto:jbl at jbldata.com]
Sent: November 20, 2009 2:42 AM
To: arocker at vex.net
Cc: tpm at to.pm.org
Subject: Re: [tpm] Single thread Perl 5.8.8 vs. Multi-threaded Perl 5.10.1

I can't think of many situations where multi-threaded perl would be beneficial.  I can understand if you were trying to make a Perl/Tk application appear snappier, or have it do graphics (animation) and accept input simultaneously.. but would there be other, more common situations where multi-threaded perl would be considered?
On Mon, Sep 21, 2009 at 4:43 PM, <arocker at vex.net<mailto:arocker at vex.net>> wrote:

> If you want high performance, you may find it easier to use
> processes with some form of IPC rather than relying on Perl threads.
People will keep trying to get the application level to do the OS's jobs.
Unfortunately, threading seems to be a problem even the OS people haven't
solved yet.

toronto-pm mailing list
toronto-pm at pm.org<mailto:toronto-pm at pm.org>

This communication contains confidential information intended only for the addressee(s). If you have received this communication in error, please notify us immediately and delete this communication from your mail box.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/toronto-pm/attachments/20091120/4ff76f03/attachment.html>

More information about the toronto-pm mailing list