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

use Perl

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

PPI (Score:1)

by Alias (5735)

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?
Plucene (Score:1)

by Smylers (2592)

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.

Smylers
Using Phalanx to answer "what is slow?" (Score:1)

by tomhukins (4457)

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