Re: perl multithreading performance
- From: Leon Timmermans <fawaka@xxxxxxxxx>
- Date: 28 Aug 2008 19:26:28 GMT
On Wed, 27 Aug 2008 23:53:09 +0200, Martijn Lievaart wrote:
Perl threading, well frankly, sucks. You may want to switch to another
language with re support that meets your needs.
Some would say all threading sucks. All approaches are either hard to get
a proper performance from or hard to get correct. At least the queue
approach perl promotes gets one of them right.
Also lets not forget that Perl at least supports preemptive threading.
Ruby doesn't at all and python has a giant interpreter lock, making it
useless for this kind of problem.
Regards,
Leon Timmermans
.
- Follow-Ups:
- Re: perl multithreading performance
- From: xhoster
- Re: perl multithreading performance
- From: Martijn Lievaart
- Re: perl multithreading performance
- References:
- perl multithreading performance
- From: dniq00
- Re: perl multithreading performance
- From: Ted Zlatanov
- Re: perl multithreading performance
- From: dniq00
- perl multithreading performance
- Prev by Date: [Q] How to seach an unmapped network drive
- Next by Date: Re: recursive filehandle
- Previous by thread: Re: perl multithreading performance
- Next by thread: Re: perl multithreading performance
- Index(es):