The OCUS Benchmark v5 Results
- Last Modified: -Here are the results of my OCUS Benchmark Version 5.
ProE users all over the world are running this benchmark on their computers by unpacking the archive and running a trailfile.
The trailfiles were created with a special script and performs several tasks. This mainly checks the speed of the CPU, the Graphics card and your Disk.
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:
Note: Results of the 64bit version can't be compared with results from the 32bit version. The 64bit version opens up a much larger assembly and needs more than 4Gb of RAM to run without swapping. If you need to compare results between 32bit OS and 64bit OS look for identical configurations in the 32bit results.
Previous versions of this benchmark:
- OCUS Benchmark v4 results (2004-2005)
- OCUS Benchmark v3 results (2000-2003)
- R20 Benchmark results (1999)
Comparing versions of Pro/E
This kind of benchmarking can also be done to compare Pro/E builds on one and the same machine.- Click here for a comparison of Wildfire 3.0 and Wildfire 4.0
- Click here for a comparison of Wildfire 2.0 and Wildfire 3.0
- Click here for a comparison of Wildfire and Wildfire 2.0
- Click here for a comparison of R2000i with R2000i2, R2001 and Wildfire with the v3 benchmark.
- Click here for a comparison of R19, R20 and R2000i with the first OCUS benchmark.
Remarks, conclusions and tips...
- See also the FAQ
- This benchmark was specifically designed for Wildfire 2.0 and Wildfire 3.0.
- Do not take these results 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.
- This benchmark needs at least 1.3Gb of RAM to run without swapping. So results from machines with less RAM are not allowed.
- 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).
- Whatever the results are. If a machine runs all tests really fast it will probably be a really fast machine, but still check for abnormal sub-scores compared to other machines. 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.