Description If the trend server is not able to write data to disk fast enough, samples will get queued up in memory until they can be written. If the trend server can't catch up it will continue to consume memory until Windows runs out of memory. It is a good idea to monitor the trend flush queue lengths to make sure the problem is not happening continually. This can indicate that the server needs to be optimized or upgraded to handle the current project size.
This Cicode file contains a function that can be called from a graphic page to monitor the current queue lengths (there are separate queues for 2-byte and 8-byte trends on each trend server). Although it is necessary to call to the trend server process to retrieve the data, this function does that in the background, storing the value in a page variable, so it can instantly return the last known value and start a separate task to update it. The function used to do the background call could be reused for calling any function on any server.
