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
Matts (1087)
Matts
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
Friday September 22, 2006
05:22 PM
bleadperl++
Just did some preliminary testing of bleadperl with some hard-hitting code (spamassassin and some other stuff). It averaged about 10% faster than 5.8.7, which is great news as far as I'm concerned.
bleadperl++
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
What OS, and what compiler? (Score:1)
For reference, which OS and compiler did you use?
As I've shown [ngo.org.uk], it can make a big difference.
Re: (Score:2)
memory (Score:1)
Re: (Score:2)
nice (Score:2)
Oooh. Nice. Thanks for this.
Does your benchmarking setup make it easy to do any sort of profiling (such as with gprof or cachegrind) to try to indentify where the remaining hotspots are?
Re: (Score:2)
Also note this was just on one code path repeated 1000 times. Different emails will produce different code paths and presumably different results.