Troubleshooting

Performance Issues While Exporting Data

By default, each export configuration is created with the autoflush option for logging set to true. This enforces every log message to be stored instantly in the target location without waiting for log buffer to be filled. That could cause some performance issues on high latency network drives (i.e. Cloud UE solution) when log level is set to Info or verbose or publishing process is producing many warnings or errors.

To resolve this problem, the configuration administrator could manually edit the configuration files and set autoFlush attribute to false, in which case the logs are buffered in the application memory and are then flushed to the log file when buffer size limit (by default 1024 bytes) is reached. Increasing the bufferSize attribute value (recommended value in such cases is 1048576, which is 1MB of memory ) could also be helpful in increasing the performance when large amount of information is logged.

The downside of modifying these options is the risk of losing critical error information in the output log file.

Example location for Export common configuration

D:\Users\Public\Documents\AVEVA\Projects\E3D3.1\AvevaPlantSample\apsdflts\IEDGateway\ExportCommonCfg.xml

Example location of export configuration:

D:\Users\Public\Documents\AVEVA\Projects\E3D3.1\AvevaPlantSample\apsdflts\IEDGateway\E3D\3.1.0\Integrity\Integrity.xml