Description: When there is a large volume of data to load into FPOMS, a delay in data loading can be encountered. The data is saved in csv files and then transferred from FP to FPOMS. An adequate size of these cvs files helps in speeding up the loading. The size is determined based on the values of the “maxfilesize” and “maxfiletime” parameters.
Symptoms: Processed SOs in FP are displayed in FPOMS GUI only after a delay of several minutes or hours.
Cause: There is a considerable number of csv files to load which is why FPOMS requires a longer time to process them.
Issue/Introduction
Delay in Loading Data into FPOMS.
Resolution
To decrease this delay, you can tune the values of the "maxfiletime" and "maxfilesize" parameters of the "enable" command of the FROMS target. Those parameters are used by the FP file writer to close the generated sod or ot csv files when one of these values has been reached by the file writer. By default, the time is set to 60 seconds and the size to 500 kB. This means that a csv file (sod or ot) will remain open 60s at max or will be close if its size reaches 500 kB.
Increasing those values should have a good impact on the latency. The more csv file sent to the FPOMS node, the more FPOMS will need time to process them. The objective is to decrease the number of csv files generated by FP and sent to FPOMS. Before increasing those parameters, monitor first your environment and find how many csv files are created per minutes or seconds. You can then start testing by increasing the values of the "maxfiletime" and "maxfilesize". Note that "maxfilesize" value should not exceed 5000 (5 MB).