comment on

[ed@deadbeef1 ed]$ perl russ.pl 
Benchmark: timing 1000000 iterations of Grep, Max, Ternary...
      Grep:  2 wallclock secs ( 2.01 usr +  0.00 sys =  2.01 CPU) @ 49
+6364.52/s (n=1000000)
       Max:  5 wallclock secs ( 3.96 usr +  0.02 sys =  3.97 CPU) @ 25
+1782.64/s (n=1000000)
   Ternary:  5 wallclock secs ( 2.32 usr +  0.00 sys =  2.32 CPU) @ 43
+0976.43/s (n=1000000)
[ed@deadbeef1 ed]$ perl -v

This is perl, v5.6.0 built for alpha-linux

Copyright 1987-2000, Larry Wall

Perl may be copied only under the terms of either the Artistic License
+ or the
GNU General Public License, which may be found in the Perl 5.0 source 
+kit.

Complete documentation for Perl, including FAQ lists, should be found 
+on
this system using `man perl' or `perldoc perl'.  If you have access to
+ the
Internet, point your browser at http://www.perl.com/, the Perl Home Pa
+ge.

[ed@deadbeef1 ed]$
[download]

damn... alpha's are fast...

In reply to Re: Algorithm Efficiency vs. Specialized Hardware? by eduardo
in thread Algorithm Efficiency vs. Specialized Hardware? by Russ

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks