Click above to get retro games delivered to your door ever month!

WarpSpeed Profiler
----------------------------------------------------------------------------------------

 WarpSpeed is a program profiler that allows you to analyze your program for
 maximum efficiency and effectiveness.  WarpSpeed provides detailed 
 information about your program because its granularity is at the function
 level.  WarpSpeed provides the following information about your program:
 
 .  Total execution time
 .  Time spent in DOS or BIOS calls
 .  Time spent in the overlay manager
 .  Time lost to the profiler
 .  Number of calls to both overlaid and nonoverlaid functions
 .  Number of overlay loads
 .  Number of overlay reloads
 .  Average times for individual functions
 .  Cumulative times for individual functions
 
 You can use WarpSpeed profile information to improve the efficiency of your
 programs by optimizing your code structure.  For example, if you have a 
 function in the root that is seldom called, putting that function in the
 overlay could save memory. You will probably not notice a loss of speed
 when the program runs because the function is not called often.  A function
 that takes a lot of time to execute could indicate that the function
 contains some inefficient code that can be optimized.  In either case, 
 running WarpSpeed again after making a change will show you how the change 
 affected the execution of your program.
 
 A big advantage of using WarpSpeed over many other profilers is that you do
 not have to change your program to run WarpSpeed.  All of the information
 gathering  and statistic gathering activities occur outside of your program.
 This means that you do not have extra profiling code within your program.
 In addition, you can profile a part of your program as easily as the entire
 program.
 
 WarpSpeed Function Overview
 
 WarpSpeed consists of two executable files that are included with the 
 WarpLink package:  

 WSPRUN.EXE and WSPSTAT.EXE.  

  Clarion users should use CNWSPRUN.EXE instead of WSPRUN.EXE. 
 
 WSPRUN is the analyzing portion of the profiler.  It generates a .WSP file
 from the  map file created by WarpLink, then runs your program, and collects
 statistics on it as the program runs.  When the program exits, WSPRUN writes
 statistics out to the same .WSP file.
 
 For each individual function within a program, WSPRUN collects:
 
 . Number of times the function is called.
 . Time spent executing the function.
 . Time spent executing the function and all lowerLevel functions that it 
   calls (cumulative time).
 
 WSPSTAT generates a report from the statistics collected by WSPRUN.  By
 default, this output goes to a file with the same name as the .WSP file,
 but uses the extension .WSS.  You can specify a file name or send it to 
 standard output so it can be piped into other programs.
 
 WSPSTAT reports the number of calls and execution time for each function by
 default.  You can specify additional information with command line options.
 
 
 Using WarpSpeed
 
 To profile your program, follow these steps:
 1. Link with the /mx command option of WarpLink to generate an expanded map
    file.
 2. Run WSPRUN.EXE with appropriate arguments and the name of your program to
    generate a data file with the extension .WSP.
 3. Run WSPSTAT.EXE with the .WSP file name to generate a report file with the
    .WSS extension.  (Or, WSPSTAT can generate a .DBF file, if desired.)
 
 You can review the .WSS (or .DBF) file, make changes to the code or program
 structure, recompile, and run the profiler again.  It's that simple.  

  Press + for WSPRUN or Press [Enter] for WSPRUN or WSPSTAT