Memory Usage
The analysis program has been written with speed, power and efficiency in mind. The amount of computer resources is dictated by the amount of data that is loaded into memory at any one time. If you are running the analysis program on a laptop, or your PC has limited memory, ensure:
- You only load the runs that you need to compare at any one time, don't load the entire day's racing unless you need to.
- Trim the runs to remove meaningless data before and after the race.
- Disable variables that are not going to be used.
If you are starting to run low on memory, then you will get a warning message from the Analysis program telling you so. If you continue loading and processing data, the Analysis program will start to run slowly as Windows is forced to use virtual memory. The amount of memory required by the Analysis program can be approximated from the total of the:
Basic program requirements
This is normally about 4MBytes.
Raw data storage
For each sample:
- an analogue channel requires 5 bytes.
- a dual axis acceleration measurement requires 6 bytes.
- a GPS position sample requires 14 bytes.
- a GPS speed sample requires 10 bytes.
- a digital channel sample requires 3 bytes.
- a frequency input (e.g. RPM) requires 5 bytes.
- a time sample requires 5 bytes.
Processed data storage
Processed data normally dominates the memory requirements. All variables are stored as IEEE 32-bit (4-byte) floating-point numbers, ranging in value from -3.402823E38 to -1.401298E-45 for negative values and from 1.401298E-45 to 3.402823E38 for positive values. So each sample of each variable requires 4 bytes. For example if 10 variables are enabled and 10 minutes of data is loaded, then the memory required for the processed data would be 10minutes x 60seconds x 100Hz x 10variables = 600kBytes.