 The OCUS R20 Benchmark
- Last modified: Mar 13 2000 -
The OCUS Benchmark is a do it yourself benchmark. It consists of:
- a part,
- a trailfile,
- a config.pro,
- the README file with the instructions and
- the UNIX script pro_bench to count the results.
In short:
You download all and run the trail file on your own computer.
Count the timelapses with pro_bench or filter out the time stamps of the trail file that
is generated by Pro/E and count the results with my web-based count tool.
What does the trail file do?
It opens the part and does many repeated actions on the part. In between
each repetition of tasks a time stamp is created.
What kind of actions does it do?
- Wireframe redraws
- Shaded mouse spins
- Shaded redraws
- Shade calculations
- Regenerations
- Menu redraws
- Saves
- Dialogue box redraws
- Mouse zooms
- Patterned X-section creation
- Family Table Verify
- Assembly creation
- Explode translations
- Screen updates
- Model Tree expansions
- Automatic Regenerations
- Perspective views
Requirements:
- Run it on Production Release Pro/ENGINEER R20 (e.g. it will not run on build 9811).
- Make sure you run a CLEAN Pro/E R20 session.
No config.pro, config.win, menu_def.pro or prodev.dat in the $PROE_LOADPOINT/text directory.
- Run it on your local temporary directory (UNIX: /usr/tmp, Windows: C:\temp)
- Minimum amount of RAM: 150Mb.
Make sure no memory swapping to disk occurs. That's not a part of this test.
Download:
I encourage you to perform this benchmark on your own computer. Check if it meets
the above requirements and download the benchmark here:
- Alternatively you can download a Windows count utility (2Kb)
It's the Windows OCUS count utility (990611 version) by Ivo Brorens from Signaal, The Netherlands
This is a Qbasic version.
For those of you that wish to run this R20 benchmark on R2000i or R19, you can download other
revision trail-file and config.pro here. Use the part from the R20 benchmark.
Other benchmarks on the net:
|
|
Number of hits since
march 11th, 1999.
|
|