Finally, you describe the thread in each process in the thread description file. You set most of Response Probe’s configuration values in this file, including the means and standard deviations for several parameters that Response Probe uses to generate each thread. Table 1 shows the parameters that you can configure.
You build the thread description file in table format with one line per parameter. The parameters can be in any order. For example, the lines
THINKTIME 0 0
CPUTIME 0 0
CYCLEREADS 100 30
FILESEEK 0 0
DATAPAGE 0 0
FUNCTION 500 0
FILEACCESS workfile.dat
FILEATTRIBUTE SEQUENTIAL
FILEACCESSMODE UNBUFFER
RECORDSIZE 2048
FILEACTION R
set the parameters for a thread that performs reads from a file. The parameters indicate that this thread
- requires no think time or additional CPU time
- reads data an average of 100 times between think times, with a standard deviation of 30 times
- uses sequential access and thus ignores file-seek time
- triggers no datapage activity
- repeatedly reads the function in the center of the codepage to simulate minimal codepage access
- reads records from the workfile.dat workload file
- reads records sequentially
- doesn’t use system cache
- reads data in 2KB chunks
- reads only (doesn’t write)
Unlike earlier versions of Response Probe, Response Probe 2.3 automatically generates and reads from an internal codepage file. The codepage file that Response Probe 2.3 uses contains a set of 1000 built-in function calls or actions that the tool can perform. This file simulates application code from which instructions are read during a process. You can tweak specific parameters after determining which parameter values best represent your application load.
