How to run the OCUS Benchmark v4

Requirements:

o       Run it on Pro/ENGINEER Wildfire, Wildfire2 or Wildfire3
        Use the appropiate trailfile.

o       You must run it in a CLEAN Pro/E session:
        Make sure the files
        	config.pro,
        	config.sup,
        	config.win,
        	menu_def.pro and
        	prodev.dat
        are NOT in the
        	[PROE_LOADPOINT]\text directory,
        	not on your C:\ root directory and
        	not in your HOME directory.

o       Run it on a local empty directory like on Windows: C:\OCUSB4
        or on UNIX: /opt/ocusb4 (you'll have to create the directory
        yourself and put all the files of the benchmark there).
        The benchmark consists of the following files:
           - ocus_bench_42_Wildfire.txt
           - ocus_bench_42_Wildfire2.txt
           - ocus_bench_42_Wildfire3.txt
           - countocus4.exe
           - ocus.scl
           - config.pro
           - ocus_bench_orig_assy.asm.26
           - ocus_bench_orig_part.prt.27
           - ocus_bench4.csh
           - ocus_tree.cfg
           - ocus4.xls
           - ocustemplate.drw.3
           - README (this file)

o       Minimum amount of RAM: 800Mb
        Make sure no memory swapping to disk occurs. That's not a part of this
        test. With higher releases you'll normally need more RAM.
        1Gb of RAM will be best.
        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. That should not exceed
        the amount of RAM seated in your system.
        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\ocusb4 (Windows) or
        /usr/tmp/bench (UNIX)

o       This local directory should only contain the benchmark files.

o       Reboot your system, wait a minute.
        UNIX: Logon as a user with a local Home directory,

o       Make sure nothing else is running on your computer:
        Shutdown any other resident programs. Especially your Virusscanner.
        Close down Intralink.

o       Turn off your screen saver.


To run it:

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 (Run CMD) or a UNIX terminal window and go (with cd)
        to your local benchmark directory.
        This is absolutely necessary in order to get the correct configuration for Pro/E.

o       Run the benchmark:
        Start Pro/E by typing your ProE startcommand in the window shell:
        For Wildfire it's probably "proewildfire", for Wildfire 2.0 or 3.0 probably "proe1".
        THIS IS VERY IMPORTANT; DON'T START PRO/E WITH YOUR OWN SHORTCUT!
        If Intralink is started as well, make sure to shut down Intralink before
        continuing.

        Tip: You can verify which configuration files are read with
          Help -> Customer Service Info (Scroll down to "Configuration files read:")

        Now select the trailfiles from Tools -> Trail/Training Files.
             - ocus_bench_40_Wildfire.txt (Wildfire version)
             - ocus_bench_40_Wildfire2.txt (Wildfire 2.0 version)
             - ocus_bench_40_Wildfire3.txt (Wildfire 3.0 version)

        Alternatively you can just start start Pro/E directly with the trailfile,
        but only if Intralink doesn´t get in the way:
        Type your Pro/E start command followed by the trail file.
             e.g.:   % proewildfire ocus_bench_40_Wildfire.txt or
                     % proe1 ocus_bench_40_Wildfire2.txt or
                     % proe1 ocus_bench_40_Wildfire3.txt
        To force Pro/E to a desired graphics option (usually OpenGL) use the -g option:
             e.g.:   % proewildfire -g:opengl ocus_bench_40_Wildfire.txt
                     Do not run it in x_windows mode.

How to count the results:

o       Windows users can use countocus4.exe to count the results.
        It will automatically count the latest trailfile.
        But you can also specify a trailfilename at the commandline:
                > countocus4 trail.txt.3
        See also:
                > countocus4 -h

o       Unix Users must run the OCUS Benchmark script (ocus_bench4.csh) with
        the -c option.
                % ocus_bench4.csh -c trail.txt.1
        See Also:
                % ocus_bench4.csh -h

    Preferably run the benchmark several times and send in the fastest benchmark.

	Note: I added an Excel file (ocusb4.xls) in which you can compile your own results.

How to send the results to me:

o       Both scripts will save all the timestamps in a text file.
        You can use these time stamps with the count utility on my site.
        www.proesite.com
        It will go directly to a form, from which you can forward the results to me.
        You will have to have direct Internet access to do so.
        Otherwise save retrieve the timestamp file on a system which does have an
        Internet connection. and go to the link above.