Allow configuration of data update rate on a per display basis
As a display creator or PI Vision administrator, I would like to be able to set the tag and/or Event Frame update rate on a display-by-display basis.
Seth Sauder
shared this idea
2 comments
-
JohnAlbers
commented
I think this is basically the same thing. To improve the response time, it would be great if you could set the number of samples pulled for a trend such that if you are zoomed in you can see 1 second data if available, but if trying to pull a year worth of data, it pulls data every 5 minutes (or something like that). PI should be able to calculate an appropriate interval.
I have a lot of trends that include 1 second data needed for troubleshooting if we have an issue, but normally I don't need that much detail. However, there is not a way of reducing the sample period that I know of.
-
Alexandre Cote
commented
That is linked to the Tech Support case #781593 where a single PI Vision display consumed 70 times more SQL resources, frequently reaching at 100% CPU, than 20 other system databases with +500 active users. The PI Vision display was referencing data from multiple AF Elements with some of them having a tons of Event Frames. As a workaround, I disabled the EF Update and set the EF Update Rate to 30 mins (was 5 seconds) on the entire PI Vision system...