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.Benchmark: timing 5 iterations of int_iterate, iterate, lex_iterate... int_iterate: 14 wallclock secs (14.19 usr + 0.12 sys = 14.31 CPU) @ +0.35/s (n=5) iterate: 53 wallclock secs (52.45 usr + 0.15 sys = 52.60 CPU) @ 0 +.10/s (n=5) lex_iterate: 47 wallclock secs (47.03 usr + 0.11 sys = 47.14 CPU) @ +0.11/s (n=5) s/iter iterate lex_iterate int_iterate iterate 10.5 -- -10% -73% lex_iterate 9.43 12% -- -70% int_iterate 2.86 268% 229% --
In reply to Re: Re: Re(2): Lesson Taught
by shotgunefx
in thread Teach him a lesson with facts
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |