RAPStore performance tuning

PrimaryFileLocation & OverflowFileLocation

These parameters control where binary files containing data to be loaded into the RAPStore are stored. For optimal system performance, these files should be stored on separate physical disk controllers than the RAPStore system itself. As well, the primary and overflow locations should be placed on separate file systems.

IOBuffferSizeMB

This parameter determines the amount of data stored in memory per database table before the data is written out to a file. Larger values for this parameter result in higher system throughput, but the parameter is constrained by the amount of available system memory.

NumIOBuffers

IO buffers are in memory storage locations that allow the system to continue to receive data when it is writing previously received data out to a file. This parameter determines the number of IO buffers created per table. Increasing the number of IO buffers beyond a value of 3 or 4 does not increase the performance of the system.

TargetFileSizeMB

This parameter determines the size of each binary file that is loaded into the RAPStore. Larger values for this parameter will increase the latency of the system. Small values for this parameter will affect system performance due to the I/O consequences of writing out and loading many individual files.

IdleBufferWriteDelaySec

This parameter determines the number of seconds to wait before data is written out to file when the system is not receiving data from the publisher. Larger values for this parameter will caused increase latency in situations where data flow is not steady. Very small values will increase the file overhead costs in the system, and will reduce performance.