My questions are:
- Does an out of memory failure in Designer when working on a report mean that in runtime the gateway will be fragile when it tries to generate the report?
- How do I prevent out of memory problems in Designer?
The report uses query tags to retrieve motor runtimes from history and subtract values one day apart to get daily runtimes, with the following queries:
1 day old value:
SELECT TAG
FROM TABLE
WHERE DATEPART(dy,t_stamp) = DATEPART(dy,(cast(GETDATE( ) -1 as date)))
AND DATEPART(hr,t_stamp) = 0
2 day old value:
SELECT TAG
FROM TABLE
WHERE DATEPART(dy,t_stamp) = DATEPART(dy,(cast(GETDATE( ) -2 as date)))
AND DATEPART(hr,t_stamp) = 0
Then I make an expression tag to subtract runtime of 1 day old from 2 day old to get the daily runtime. I add those tags to a daily report. I forgot to set the scan class to something slower so it is the default scan class for all these tags. There are 66 tags in all (22 runtimes, 3 tags for each runtime)
When I add the 22 daily runtime tags to a report and go to Preview, after 30 minutes it still has not completed the Preview:
Looking at the console, I see memory errors:
When I try to close Designer, it won’t close:
I do not see the gateway (on which I am using Designer) running out of memory:
The only way to close Designer is to kill the Java web launcher:
My biggest concern is that if the report, which is scheduled to save to a PDF every night at 1 am, runs out of memory resources when it is generated can it crash the gateway? Can it severely impact gateway performance?
If this is only a Designer problem, how is this fixed? Do reports, query tags, or expression tags inherently have greater resource demands? Should I avoid doing reports in Ignition?