comment on

[mike@prometheus PerlMonks]$ ./Russ.pl
Benchmark: timing 1000000 iterations of Grep, Max, Ternary...
      Grep: 16 wallclock secs (14.74 usr +  0.10 sys = 14.84 CPU) @ 67
+385.44/s (n=1000000)
       Max: 37 wallclock secs (36.62 usr +  0.00 sys = 36.62 CPU) @ 27
+307.48/s (n=1000000)
   Ternary: 39 wallclock secs (38.23 usr +  0.01 sys = 38.24 CPU) @ 26
+150.63/s (n=1000000)

[mike@prometheus PerlMonks]$ perl -v

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

[mike@prometheus PerlMonks]$ uname -mrs
Linux 2.2.16-1 i586

[mike@prometheus PerlMonks]$ free
             total       used       free     shared    buffers     cac
+hed
Mem:         63032      61552       1480      20196       2012      23
+872
-/+ buffers/cache:      35668      27364

[mike@prometheus PerlMonks]$ cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 5
model           : 2
model name      : Pentium 75 - 200
stepping        : 12
cpu MHz         : 199.436
[download]

In reply to Re: Algorithm Efficiency vs. Specialized Hardware? by mdillon
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.


XP is just a number
	PerlMonks