http://yaketyhack.blogspot.com/2010/07/threading-perl-vs-python.html

I’ve done quite a log of threading in Perl, and am aware of it’s limitation. I said “I doubt” instead of “I know” because I think that’s the only responsible way to speak when referring to how threads perform in a language in general. There’s so many different ways to use them, and the different threading models will have different strengths and weaknesses for each.

I agree with you about list vs shifting (makes sense right? – shifting does more work)

And yes, your explanation of the python string advantage makes sense. It can just pass the references around.

Cheers

By the way, I just realized that Python is probably even faster with string arguments (when compared to Perl) because I think it uses immutable strings. Perl actually copies those strings every time when passing by value.

2. I know it, you – idiot. I am writing this because I think that doing the right thing.
3. Your benchmarks are meaningless with such attitude. You optimize python code and using bad written Perl code. WOW, it’s a very correct comparison.

2. This isn’t a task – none of these subroutines do anything useful. Are you an imbecile or do you just play one on my blog?
3. Er, no.

@juster – I didn’t mention python coroutines, you did. You’re moving the goalposts.

Most of my code has to work on Win32 so Coro is not particularly useful to me and fork is built over threads in any case.

Checkout the mandelbrot or chameneos benchmark at the debian language shootout:
http://shootout.alioth.debian.org/u32q/perl.php

I’m not bashing perl, just perl “threads”. Use fork() or the Coro module (omg coroutines). Yes on a multi-core machine Coro still outperforms threads. Try it yourself… benchmark!

PS I agree using unnamed subroutine arguments is ridiculous.

2. In such small tasks – always
3. If you don’t care, use “range” (not “xrange”) in python code

2. How often do you write Perl subroutines without explicitly unpacking @_? Your version of f2 is disingenuous.
3. Don’t care.
4. Yep, got that wrong, sorry. Note (if you’re trying to improve your English/manners), Nilson pointed that my error with f2a much more nicely.

You rude git.

@Anonymous – I considered using Benchmark.pm, but I don’t know the Python equivalent. You’re right though, readers are probably more interested in intra-Perl comparison.

@Juster – I suspect proper parallelizable code on a multi-core system will make Perl threads look good in comparison to Python threads. And if you’re just trying to avoid blocking, why not use something like AnyEvent (or is that your point)?

@Nilson – Thanks – I’ll fix up f2a (and call the Python in a non-void context) and update the post.