Mac OS X built-in benchmark!?

[hulkaros]

Do this:
-Locate and open the Terminal (Inside Utilities folder which resides inside the Applications folder)
-At the prompt type...

openssl speed

...and press enter
-Wait for anything between 5-10 minutes maybe
-Numbers & words will appear into the Terminal which indicate how fast ANY computer running UNIX, LINUX, MAC OS X, etc. supposedly is...

Have fun

For even more fun go here:
http://www.macosxhints.com/article.php?story=20020113045343563

I just hope that this will NOT start a PC vs MAC war but instead will let us have some fun

 

[Ricky]

My results:

                  sign    verify    sign/s verify/s
rsa  512 bits   0.0071s   0.0006s    140.3   1580.0
rsa 1024 bits   0.0374s   0.0022s     26.8    461.6
rsa 2048 bits   0.1409s   0.0063s      7.1    158.7
rsa 4096 bits   2.5400s   0.0400s      0.4     25.0
                  sign    verify    sign/s verify/s
dsa  512 bits   0.0086s   0.0101s    115.7     98.9
dsa 1024 bits   0.0289s   0.0361s     34.6     27.7
dsa 2048 bits   0.1025s   0.1074s      9.8      9.3

Could a UNIX guru come here and figure out what this means? By the way, I was running about a half-dozen apps at the time.

 

[dsibilly]

I, too, am unsure as to what these number mean, but here's my results from my po' lil' Beige G3. I didn't have squat running at the time: I ssh'd into the machine from a computer @ work and ran the benchmark, so the Finder, Dock, etc. weren't even running.

sign verify sign/s verify/s
rsa 512 bits 0.0096s 0.0010s 104.2 1048.2
rsa 1024 bits 0.0576s 0.0032s 17.4 313.1
rsa 2048 bits 0.3873s 0.0117s 2.6 85.3
rsa 4096 bits 2.7275s 0.0433s 0.4 23.1
sign verify sign/s verify/s
dsa 512 bits 0.0092s 0.0112s 108.8 89.5
dsa 1024 bits 0.0317s 0.0391s 31.6 25.6
dsa 2048 bits 0.1138s 0.1419s 8.8 7.0

 

[wdw_]

Here's mine:

                  sign    verify    sign/s verify/s
rsa  512 bits   0.0031s   0.0003s    323.3   3316.1
rsa 1024 bits   0.0181s   0.0010s     55.3   1003.5
rsa 2048 bits   0.1213s   0.0036s      8.2    276.0
rsa 4096 bits   0.8517s   0.0134s      1.2     74.4
                  sign    verify    sign/s verify/s
dsa  512 bits   0.0029s   0.0036s    344.0    281.5
dsa 1024 bits   0.0100s   0.0120s    100.2     83.4
dsa 2048 bits   0.0353s   0.0431s     28.3     23.2

 

[kommakazi]

Here's my 350 overclocked to 400mhz G3 B&W Tower results:

sign verify sign/s verify/s
rsa 512 bits 0.0074s 0.0007s 135.5 1372.1
rsa 1024 bits 0.0449s 0.0025s 22.3 407.4
rsa 2048 bits 0.2984s 0.0091s 3.4 110.0
rsa 4096 bits 2.1040s 0.0337s 0.5 29.7
sign verify sign/s verify/s
dsa 512 bits 0.0072s 0.0087s 138.6 115.5
dsa 1024 bits 0.0247s 0.0301s 40.5 33.3
dsa 2048 bits 0.0884s 0.1092s 11.3 9.2

 

[andymac]

rsa is the algorithm which secure the communication in net using a socalled public/private key scenario. the different bit size indicate the key length, longer key indicates more security.
of course the calculation of a key takes time, that's what "sign" means.
Vice versa, when we receive some call from others through secured channel, we gonna to verify the key (public key of the sender) and this process is sure easier than generating one.
das should be in the same category.

 

[ddma]

Seems that the raw preformance (I hope you know I am talking about RAW PREFORMANCE, non-Velocity Engine-optimized) on the PeeCee world is now much better. What if Mac OS X could be running native on a PeeCee? A dream machine!

 

[Captain Code]

sign verify sign/s verify/s
rsa 512 bits 0.0073s 0.0007s 136.6 1401.7
rsa 1024 bits 0.0437s 0.0024s 22.9 416.5
rsa 2048 bits 0.2924s 0.0089s 3.4 112.5
rsa 4096 bits 2.0640s 0.0330s 0.5 30.3

sign verify sign/s verify/s
dsa 512 bits 0.0070s 0.0085s 143.5 117.0
dsa 1024 bits 0.0240s 0.0296s 41.7 33.7
dsa 2048 bits 0.0860s 0.1073s 11.6 9.3

SSH'd into my machine. Seti@Home was running at the time.

 

[fryke]

Hmm... While my PowerBook G4/500 does the following in the first few lines:

Doing md2 for 3s on 8 size blocks: 137430 md2's in 2.33s
Doing md2 for 3s on 64 size blocks: 49360 md2's in 2.39s
Doing md2 for 3s on 256 size blocks: 16579 md2's in 2.38s
Doing md2 for 3s on 1024 size blocks: 4461 md2's in 2.41s

My PC on Linux seems to be more exact about the '3s' thing:

Doing md2 for 3s on 8 size blocks: 179926 md2's in 2.95s
Doing md2 for 3s on 64 size blocks: 63890 md2's in 3.00s
Doing md2 for 3s on 256 size blocks: 21619 md2's in 3.00s
Doing md2 for 3s on 1024 size blocks: 5927 md2's in 3.00s

So I couldn't say whether this openssl test is appropriate to measure processor speed, if it's that unreliable...