![]() Xbench-0.2: results/name_of_your_linux_box.out.Kernel 2.0.0 compilation: 5 - 30 minutes, depending on the real performance of your system.BYTE Magazine's BYTEmark benchmarks beta release 2 (partial results).įor tests 4 and 5, "(partial results)" means that not all results produced by these benchmarks are considered.UnixBench benchmarks version 4.01 (partial results).xbench-0.2 (with fast execution parameters).Whetstone version 10/03/97 (latest version by Roy Longbottom).Kernel 2.0.0 (default configuration) compilation using gcc.I have selected five different benchmark suites, trying as much as possible to avoid overlap in the tests: Applications benchmarks should consist of commonly executed tasks on Linux systems.Results of synthetic benchmarks should not be averaged into a single figure of merit (that defeats the whole idea behind synthetic benchmarks, with considerable loss of information).Each synthetic benchmarks should exercise a particular subsystem to its maximum capacity.There should be a mix of synthetic benchmarks and application benchmarks (with separate results, of course).Benchmarks should provide simple figures reflecting the measured performance.All source code for the software used must be freely available on the Net, for obvious reasons.Ideally, the entire benchmark set should take about 15 minutes to complete on an average machine. ![]() When it comes to comparative benchmarking (various runs), nobody wants to spend days trying to figure out the fastest setup for a given system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |