Collapse all Symbian^3 Product Developer Library

Configuring the base_perf_f32_env.ini File

Describes the common configuration items for each test case that can be configured in the base_perf_f32_env.ini file.

Note: Changing this configuration file has an impact on the entire test suite as each test uses the contents of this file for its specific test scenario.

The configurable items in the base_perf_f32_env.ini file are listed in the following table:

Field name	Description
csvFileName	Defines the default name of the .CSV file and its location. The data within this parameter can be in one of the following formats: <Drive Letter>: \<name of file>.csv - OR - <Drive Letter>: \<location>\<name of file>.csv The .CSV file contains readable test results. By default, this file is named f32-perfResults.csv and is stored in the C: drive. Note: This value is used by all test cases.
threadname	Defines the default name of the thread handle to be created, for all test cases.
stacksize	Defines a default integer that specifies the stack size allocated to the thread handle. The default is set to 0x2000. This value is used by all test cases.
minheapsize	Defines a default integer value that specifies the minimum heap size allocated to the thread handle. By default, this is set to 256 KB or 0x100. Note: This value is used by all test cases.
maxheapsize	Defines a default value that specifies the maximum heap size allocated to the thread handle. By default, this is set to 1 MB or 0x100. Note: This value is used by all test cases.
ownertype	Defines a default `TOwnerType` enumeration value that defines the ownership of this thread handle. By default, this is set to `EOwnerProcess`. Note: This value is used by all test cases.
threadpriority	Defines a default `TThreadPriority` enumeration value that defines the priority of the thread handle. By default, this is set to `EPriorityLess`. Note: This value is used by all test cases.
driveName	Default writable drive. This drive is used for creating a temporary test directory structure for test cases. This value must be the character of the drive, followed by a semicolon. The default value is E:. The data within this parameter must be in the following format: <Drive Letter>: Note: Modifying this value impacts the location where the test cases create its test directory structure, and also the location on which the tests performs their operations.
formatDrive	Defines a boolean value that indicates whether a drive is to be formatted during a test. This must be a boolean value. By default, it is set to `EFalse`. Note: This value is used by all test cases.
baseDirName	Defines the name of the parent test directory used to store the test directory. The data within this parameter must be in the following format: {Default, driveName}\< name of base directory>\ Note: This value is used by all test cases. Therefore, altering this value affects all test cases.
subDirName	Defines the name of the actual test directory that is used for storing test files. Each sub-directory created has the same name. For example, if the name of the test directory is dir, the first directory that will be created is dir, the second sub-directory created is also called dir, and so on. Ensure that this name does not contain a dot character (‘.’). Note: This value is used by all test cases. Therefore, altering this value affects all test cases.
fileBaseName	Defines the name of the test file that is used for each test case. Each file will be appended with an incrementing number. For example, if the file base name is file.txt then the name of the first file that will be created is file1.txt. Ensure that the name of the file does contain a dot character (‘.’). You can use one of the following formats: <name of file>.<extension name> - OR - <name of file> Note: This value is used by all test cases. Therefore, altering this value affects all test cases.
fileData	Defines the content of each file created. Note: This value is used by all test cases.
dirTreeDepth	Defines an integer number that represents the default number of directories to be created in the base directory. This value is used by all test cases. Therefore, altering this value affects all test cases, and the test directory structure that each test case creates and uses. Note: Based on the actual size of the directory structure that is created, use an MMC card of an appropriate size.
numOfFiles	Defines an integer number that represents the default number of files to create in each directory. This value is used by all test cases. Therefore, altering this value affects all test cases, and the test directory structure that each test case creates and uses. Note: Based on the actual size of the directory structure that is created, use an MMC card of an appropriate size.
fileSize	Defines an integer number that represents the default file size (in bytes) of each file to create. By default, this is set to 128 Kb or 1024 x128 bytes. Note: Modifying this value affects all tests within this suite, as all test cases use this file size while creating files for its test directory structure. Also note that the block sizes you are using while manipulating the file size as RFile write API tests are also affected. For example, if you are using a `blockSize` of 65536 bytes for `XLBytes`, ensure that the file size set is equal to or greater than 131072 bytes. As you cannot write 65536 bytes to a file that has a set size of less than (blockSize + blockSize).
XSBytes	Defines an integer number that represents a `blockSize` (in bytes) that can either be read into a file or written to a file. Modifying this value affects all RFile read test cases and all RFile write test cases. XSBytes represents an extra small number of bytes. By default, this value is 16 bytes.
SBytes	Defines an integer number that represents a blockSize in bytes that can either be read into a file or written to a file. Modifying this value affects all RFile read test cases and all RFile write test cases. SBytes represents a small number of bytes. By default, this value is 512 bytes.
MBytes	Defines an integer number that represents a blockSize in bytes that can either be read into a file or written to a file. Modifying this value affects all RFile read test cases and all RFile write test cases. MBytes represents a medium number of bytes. By default, this value is 512 bytes.
LBytes	Defines an integer number that represents a blockSize in bytes that can either be read into a file or written to a file. Modifying this value affects all RFile read test cases and all RFile write test cases. LBytes represents a large number of bytes. By default, this value is 32768 bytes.
XLBytes	Defines an integer number that represents a blockSize in bytes that can either be read into a file or written to a file. Modifying this value affects all RFile read test cases and all RFile write test cases. XLBytes represents an extra large number of bytes. By default, this value is 65536 bytes.

Parent topic: F32 Performance Test Suite