📖HomeBack The new 'Memory Usage' page in the General section breaks down the memory usage of the ClearSCADA server. This can be used with the snapshot facility to diagnose memory usage related problems.
A problem that could occur would be too much historic data being logged and the historian not being able to write it all to disk fast enough. This has the effect of keeping all the information in the memory of the server, and in this case you would expect to see the Raw section of memory usage to increase. A similar problem could be seen for the event journal.
This feature does not provide the definitive solution to memory problems. But it does give a general guide into the area of the product to investigate and is a good starting point.
Ways to alleviate memory problems
Add more memory, which seems obvious, but getting to the 32bit limit (4GiB) should be a first start.
Lower the 'QueryRowLimit' registry key, which controls the maximum number of records that can be returned in a single query, this defaults to 1,000,000 and as such can use a very large amount of memory for a inefficient query.
Lower the Historic and Event Journal Cache settings. These determine the amount of memory allocated for storing historic and event journal records. While this data is normally stored on disk, the cache is used to search and process the data and it will remain in the cache until that memory is required for new searches etc. This provides better search performance as data does not need to be constantly loaded into and out of memory.