How to run the OCUS Benchmark
(This information is also included in the archive: see README file)
- Last modified: Mar 27 2003 -
o Run it preferably on Pro/ENGINEER Release R2000i.
If you want to run it on R2000i2 use the seperate R2000i2 trailfiles.
But R2000i will have the best results; R2000i2 is much slower.
o Make sure you run a CLEAN Pro/E session.
No config.pro, config.win, menu_def.pro or prodev.dat in the
$PROE_LOADPOINT/text directory and not in your HOME directory.
o Run it on a local empty directory like on UNIX: /usr/tmp/ocus_bench,
or on Windows: C:\temp\ocus_bench (you'll have to create the directory
yourself and put all the files of the benchmark there)
o Minimum amount of RAM:
small: 256MB.
LARGE: 512Mb.
Make sure no memory swapping to disk occurs. That's not a part of this
test.
Windows users can use the Performance Tab in the task manager to verify
this. Reboot your system first and make note of the Peak Memory Usage
(Commit Charge) after the benchmark has finished.
Unix users could use the unix swap command to get current swap info.
o Run the benchmark under normal working conditions.
Like: normal screen resolution, color depth, refresh rates.
Minimum: 1280x1024, 16bpp, 70Hz
Here are the steps to follow for running the benchmark:
o First unzip the file.
(UNIX: gunzip.exe can be found under the loadpoint of Pro/E in the
dsrc directory. tar is a standard unix command).
Put all files in a local empty directory like c:\temp\bench (Windows) or
/usr/tmp/bench (UNIX)
o This local directory should only contain the benchmark files.
o Make sure nothing else is running on your computer.
Reboot it, wait a few minutes and then do the test.
o Disable your network connection if it is possible.
o UNIX: Logon as a user with a local Home directory,
o Turn off your screen saver.
o Turn off your desktop background image.
o Run the test with absolutely NO configuration options of your
own.
Remove the config.pro, config.sup, config.win, menu_def.pro and prodev.dat
files from the text directory in the loadpoint of Pro/E and from your HOME
directory. Windows users should also verify the directory c:\ for
configuration files.
o open a MS-DOS shell window or a UNIX terminal window and go (with cd)
to your local benchmark directory.
o Run the benchmark:
Start Pro/E by typing proe2000i (or proe2000i2) in the window shell.
This is very important; don't start Pro/E with your own shortcut!
Tip: You can verify which configuration files are read with
Help -> Customer Service Info (Scroll down to "Configuration files read:")
Now select one of the trailfiles from Utilities -> Trail/Training Files.
ocus_bench_31.txt (normal version)
ocus_bench_31_light.txt (small version)
ocus_bench_31_2000i2.txt (normal R2000i2 version)
ocus_bench_31_light_2000i2.txt (small R2000i2 version)
Alternatively you can just start start Pro/E directly with the trailfile.
Type your Pro/E start command followed by the trail file.
e.g.: % proe2000i ocus_bench_31.txt
To force Pro/E to a desired graphics option (usually OpenGL) use the -g option:
e.g.: % proe2000i -g:opengl ocus_bench_30.txt
Do not run it in x_windows mode.
o Check your Pro/E session on the following points:
1 The application manager is not started.
2 Shaded view redraws and shaded mouse spins are
really shaded.
3 Model Tree expansion test is not much faster than the rest.
How to count the results:
o Unix Users must run the OCUS Benchmark script (ocus_bench) with the
-c option.
% ocus_bench -c trail.txt.1
o Windows users can use a batch program (ocus_c30.bat) to count the results.
> ocus_c30.bat trail.txt.1
The batch file will call the included grep.exe (*) and run a QBasic
program (OCUS_C30.BAS). The QBasic program will only run on a short
directory path (QBasic problem). If there is a directory with a name
longerthan 8 characters in your path then the program will fail.
Preferably run the benchmark several times and send in the fastest benchmark.
How to send the results to me:
o Both scripts will save all the time stamp in a text file.
You can use these time stamps with the OCUS Benchmark count utility on my site.
http://utopia.knoware.nl/~ocorten
It will go directly to a form, from which you can forward the results to me.
If you really can 't use my online count utility to send in the results
then you can fall back to the following procedure.
Make sure to use the format described below exactly so I can process
the mail automatically.
Send the results back (to olafc@molding.fico.nl),
in this exact format (comma seperated fields):
Vendor, Type, CPU type, CPU speed, Graphics, RAM, Swap, disk type and speed,
OS type and version, Pro/E Release, buildcode, Pro/E graphics option (e.g. OPENGL),
Display resolution, display color depth, display refresh rate, email address
followed by the output generated by pro_bench -c (UNIX) or ocus_c30 (Windows)
---- EXAMPLE ------------------------------------------------
SGI, Solid Impact, R10000, 195 MHz, Impact graphics, 588 Mb RAM, 600Mb swap,
disk ?, IRIX 6.2, R2000i, 2000350, OPENGL, 1280x1024, ? ,70Hz, olafc@molding.fico.nl
23-Nov-00 10:08:09 = start
23-Nov-00 10:22:00 = 831 seconds = Retrieve Assembly (CP)
23-Nov-00 10:24:12 = 132 seconds = 7 wireframe redraws (GR)
23-Nov-00 10:26:51 = 159 seconds = 7 wireframe redraws with DTMS (GR)
23-Nov-00 10:30:05 = 194 seconds = 2 hiddenline redraws (GR)
23-Nov-00 10:30:39 = 34 seconds = Turn on FastHLR (CP)
23-Nov-00 10:32:41 = 122 seconds = 25 hiddenline redraws with FastHLR (GR)
23-Nov-00 10:35:17 = 156 seconds = 15 shaded mouse spins (GR)
23-Nov-00 10:37:21 = 124 seconds = 130 shaded redraws (GR)
23-Nov-00 10:39:56 = 155 seconds = 4 shade calculations (CP)
23-Nov-00 10:42:45 = 169 seconds = 60 wireframe mouse zooms (GR)
23-Nov-00 10:47:02 = 257 seconds = 2 advanced shaded mouse zooms (GR)
23-Nov-00 10:48:43 = 101 seconds = 300 menu redraws (GU)
23-Nov-00 10:50:41 = 118 seconds = 300 dialogue box redraws (GU)
23-Nov-00 10:53:45 = 184 seconds = 6 regenerations (CP)
23-Nov-00 10:56:55 = 190 seconds = 60 Part Saves (DI)
23-Nov-00 10:59:58 = 183 seconds = 8 Explode translations (GR)
23-Nov-00 11:02:33 = 155 seconds = 6 Screen updates (GR)
23-Nov-00 11:05:27 = 174 seconds = 11 Model Tree Expansions (GU)
23-Nov-00 11:08:15 = 168 seconds = 18 Automatic Regenerates (CP)
23-Nov-00 11:10:25 = 130 seconds = 18 X-Section shows (GR)
23-Nov-00 11:12:21 = 116 seconds = 25 Perspective views (CP)
23-Nov-00 11:14:35 = 134 seconds = 1 Assy Mass Properties calculations (CP)
23-Nov-00 11:19:26 = 291 seconds = 10 Global Interference checks (CP)
23-Nov-00 11:21:38 = 132 seconds = 1 Assy IGES export (CP+DI)
23-Nov-00 11:24:42 = 184 seconds = Create Drawing (CP)
23-Nov-00 11:27:30 = 168 seconds = 100 Show Dimensions (CP)
23-Nov-00 11:29:17 = 107 seconds = 1 Regenerate Views NO HIDDEN (CP)
23-Nov-00 11:31:13 = 116 seconds = 1 Regenerate Views HIDDEN LINE (CP)
23-Nov-00 11:34:46 = 213 seconds = 1 Postscript file creation (CP+DI)
23-Nov-00 11:38:52 = 246 seconds = 1 DXF file creation (CP+DI)
CPU related tasks (CP) = 3079 seconds
Graphics related tasks (GR) = 1781 seconds
GUI related tasks (GU) = 393 seconds
DISK related tasks (DI) = 781 seconds
Total = 5443 seconds
---- EXAMPLE ------------------------------------------------
|