How to run the OCUS Benchmark v5

Requirements:

o       Run it on Pro/ENGINEER Wildfire 2.0 or Wildfire 3.0
        Use the appropiate trailfile.
        The 64bit versions will use more than 4Gb of RAM,
        so you'll definitely need 64bit architecture.


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
        	protk.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:\OCUSB5
        or on UNIX: /opt/ocusb5.
        The benchmark consists of the following files:
           - config.pro
           - config.win
           - countocus5.csh
           - countocus5.exe
           - ocus.jpg
           - ocusb5.scl
           - ocusb5.xls
           - ocustemplate.drw.5
           - ocus_bench_50-64bit_wildfire2.txt
           - ocus_bench_50-64bit_wildfire3.txt
           - ocus_bench_50_wildfire2.txt
           - ocus_bench_50_wildfire3.txt
           - ocus_bench_largest_assy.asm.13
           - ocus_bench_large_assy.asm.8
           - ocus_bench_orig_assy.asm.29
           - ocus_bench_orig_part.prt.47
           - ocus_tree.cfg
           - README.txt (this file)


o       Minimum amount of RAM:
        o Normal version: 1Gb (preferably more)
        o 64bit version: 5Gb
        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.
        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       Minimum amount free diskspace:
        o Normal version 300Mb
        o 64bit version: 2.5Gb
        During the benchmark a very large IGES file is being created.

o       Run the benchmark under normal working conditions.
        Like: normal screen resolution, color depth, refresh rates.
        Minimum: 1280x1024, 16bpp, 70Hz

o       It is essential to start Pro/E from a DOS-prompt or a UNIX-shell
        in the benchmark directory and then open the appropiate trailfile.



Here are the steps to follow for running the benchmark:

o       First unpack the file.
        Put all files in a LOCAL empty directory like c:\temp\ocusb5 (Windows) or
        /usr/tmp/OCUSB5 (UNIX)

o       This local directory should only contain the benchmark files.

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

o       Make sure nothing else is running on your computer:
        Shutdown any not needed resident programs like virusscanner, etc.
        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 protk.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 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_50-64bit_wildfire2.txt (64bit Wildfire 2.0 version)
           - ocus_bench_50-64bit_wildfire3.txt (64bit Wildfire 2.0 version)
           - ocus_bench_50_wildfire2.txt (Wildfire 2.0 version)
           - ocus_bench_50_wildfire3.txt (Wildfire 3.0 version)

        Tip: If you accidentally clicked a 64bit version then kill Pro/E by ending the xtop and nmsd processes.

        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.:   % proewf2 ocus_bench_50_wildfire2.txt or
                     % proewf3 ocus_bench_50_wildfire3.txt

How to count the results:

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

o       Unix Users must run the countocus5.csh script:
                % countocus5.csh -c trail.txt.1
        See Also:
                % countocus5.csh -h

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

        Note: I added an Excel file (ocusb5.xls) in which you can compile and compare 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 www.proesite.com.
        But the counttools 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 the timestamp file on a system which does have an
        Internet connection and go to link above to upload your results.