Benchmarking

  2006-12-24 00:00:02
IMHO speed is overrated. Benchmarks execute hundreds of millions of the same instructions, taking ages to finish. In real life that is almost never the case, except for some pretty processor intensive jobs you'd never dream to write in a scripting language. Telling an interpreter it is slow makes just as much sense as telling a bicycle it is slow. Although that is true, millions of Dutchmen find good reasons to use them every day. If you need to go a long way, you simply won't use a bicycle. If an interpreter is too slow for a job, you grab a compiler. It is as simple as that. 
  PNG Image  PNG Image  PNG Image
  Related tags  


This particular article has been collected via RSS syndication. We apologize if it's too brief.
If You wish to publish articles on LinuxStreet.net please contact us.


  Similar articles found on LinuxStreet  
ImageVista, Linux and OS X benchmarking
ImagePhoronix Test Suite Brings Benchmarking To Mac OS X
ImagePhoronix Test Suite Brings Benchmarking To Mac OS X
ImageOpenGL Benchmarking On Linux Reaches New Heights
ImagePhoronix Test Suite Brings Benchmarking To Mac OS X
ImageOpenGL Benchmarking On Linux Reaches New Heights
ImageMail server benchmarking with Postal
ImagePhoronix Test Suite 0.2
ImagePhoronix Test Suite 0.2 Adds New Features
ImageDefining The Phoronix Test Suite

Leave a comment on this article


Captcha

  
Check this if the code you see is not readable and resubmit the form.
(Data you entered will be preserved)



  

Comments (0)