The first benchmark was from a linux 2.2 kernal running 5.6.0 with an Intel Celeron 400MHZ with 256MB.
On a ultrasparc 10 running linux 2.2 with 256 MB (5.6.1) I get similar results...
Benchmark: timing 5 iterations of int_iterate, iterate, lex_iterate...
int_iterate: 14 wallclock secs (14.19 usr + 0.12 sys = 14.31 CPU) @
iterate: 53 wallclock secs (52.45 usr + 0.15 sys = 52.60 CPU) @ 0
lex_iterate: 47 wallclock secs (47.03 usr + 0.11 sys = 47.14 CPU) @
s/iter iterate lex_iterate int_iterate
iterate 10.5 -- -10% -73%
lex_iterate 9.43 12% -- -70%
int_iterate 2.86 268% 229% --
Regardless... what does this actually mean? Not much. The iteration test isn't usually what the problem is. Usually it's all the stuff in-between that is the bottleneck and how fast the turn-around time is. It to me is a useless metric... (unless you're writing a video driver or such.) I think it's a case of not seeing the forest through the trees. If I was making a renderer or such that needed low-level speed I would just use XS or Inline, but the biggest thing for me is, how quick can I get a job done and how quick can I implement changes and to me Perl fits the bill perfectly.
"To be civilized is to deny one's nature."