Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Journal of nicholas (3034)

Wednesday April 19, 2006
09:22 AM

what is slow?

[ #29370 ]

I'm thinking about slow. Specifically I'm wondering what is slow? As in, what important things written in Perl are slow, and seem to be more slow than they should be. Perl applications that appear to be giving the interpreter heartburn. I'm looking for volunteers for experimenting on.

Specifically, there's an item in perl todo titled Profile Perl - am I hot or not? But it's not clear to me what would be good candidate Perl source code to run against the interpreter to profile it. So, dear lazyweb, useful suggestions please...

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • PPI is slow. Really slow. It handles about 1500 lines per gigacycle (on average) but when you run it against a big directory of stuff, it still feels really slow.

    I've optimised (and in a few places micro-optimised) the hell out of it. I really don't know what more I can do. Maybe there's something there for you.

    One clue that sticks out is that UNIVERSAL::isa (the function) shows up in some of my profiling reports for it.

    Perhaps there's something that could be done to make UNIVERSAL::isa faster?
  • I believe that Plucene's slowness is the main thing preventing it from being viable. Or at least it was at YAPC Belfast; things may have changed since then.


  • The Phalanx Project [] identifies important, commonly used modules. You could use the modules listed to discover where people might care about Perl running slowly.