Stories
Slash Boxes
Comments
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 ]

acme (189)

acme
  (email not shown publicly)
http://www.astray.com/

Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

Journal of acme (189)

Friday December 14, 2007
05:49 AM

Perl is fast at log parsing

[ #35100 ]

It's very interesting to see Tim Bray's Wide Finder Project results. Essentially, it's a log parsing benchmark. The twist is that it's running on a Sun SPARC Enterprise T5120 Server. This is a Niagara II-based server which has eight CPU cores, each of which is able to run eight threads - effectively 64 concurrent threads. Why is this important? Because it's getting harder to make chips go faster, so instead chips are going multicore.

This really started because Tim wanted to play with Erlang, but the initial performance was terrible. Currently top of the list is Perl, with a program by Sean O'Rouke. It's compact but beautiful code.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It was fun to write. It just goes to show than knowing a bit about hardware and systems usually counts for a lot more than having particular language facilities. Oh, and that Perl's regex engine rocks unhealthily hard.

    Note that this unfortunately breaks [gmane.org] in blead, where the mmap()ed string is copied to preserve $1 and friends, but it should be easily fixable after the release.