The OCUS Benchmark v3 Results

- Last Modified: -

Here are the results of my OCUS Benchmark Version 3.

ProE users all over the world are running this benchmark on their computers by unpacking the archive and running a trailfile.

The trailfile was created with a special ocus_bench script and performs several tasks. This mainly checks the speed of the CPU and the Graphics card.

If you want to run it yourself you can download it here. Calculate and send your results with my online count utility.

Below are the results I received so far. Scores are in seconds, lower is better:

• Total score

• CPU tests only score, Graphics test only score, GUI test only score, DISK test only score

You can also:

• view the Total score including sub-scores
• view the Full results
• Search the results pages
  

• view the top 10 per task scores
• view the scores sorted by vendor
• view the results of the top 25 as a graph (50Kb).

• Here you can view the light v3 results
  The benchmark is also available as a light version for machines with not enough memory to run the full version.

• Here you can view the previous R20 Benchmark results of 1999
  The results of the previous release of the benchmark.

• Click here for a comparison of R2000i with R2000i2, R2001 and Wildfire This kind of benchmarking can also be done to compare Pro/E builds on one and the same machine.

• Here are results from a user who did a comparison on an IBM Thinkpad between WindowsXP and Linux RedHat 9.0 with different Window Managers with the (withdrawn) Wildfire OCUS 3.2 benchmark.
• And here another comparison with an AthlonXP 1700MHz GeForce 2Ti (64Mb) between WindowsXP and different Linux distributions with the (withdrawn) Wildfire OCUS 3.2 benchmark.

Remarks, conclusions and tips...

• This benchmark was specifically designed for R2000i. The normal trailfile will yield incorrect results when run with other releases.
  You can run this benchmark with R2000i2 and R2001 with special trailfiles (Download the v3.3 Benchmark). But the results will still not be comparible with R2000i since the newer releases are much slower with many tasks.
• Do not take these result for granted. You can make a lot of adjustments on every machine to make Pro/E run faster or slower. Furthermore, note that these benchmarks were performed at all kinds of sites and with a lot of different builds. This surely influences the results.
• Some of you are concerned with the fact that vendors are entering results as well. Are they really reliable? My opinion in this is, that if a vendor performs special tricks to get abnormal fast results he will soon be uncovered by users who have such a machine as well. If you consider buying a machine based on these results why not perform this benchmark on a demonstration model by that vendor and see if the fast results can be reproduced under normal working conditions?
  
• This benchmark needs at least 512Mb of RAM to run without swapping (the light version needs 256Mb). So results from machines with less are not accurate at the end of the test.
• If your machine performs bad only on specific tasks verify if you've really removed all configuration files in the $PROELOADPOINT/text and $HOME directory (usually C:\ on Windows).
• Floating licenses could make a difference, since Pro/E has to check the network for free licenses.
• I did not add any prices. Too much uncertainty ... You'll have to calculate your own price/performance values.
• Whatever the results are. If a machine runs all tests really fast it will probably be a really fast machine (check for no abnormal sub-scores). If it is really slow on the other hand you will first have to check if this is not some kind of configuration issue before judging the computer.

Future recommendations: