kgamble
December 14, 2021, 10:36pm
1
I know there is a config java additional arg for project scan frequency, and it used to be in the upgrade guide but I can’t find it anymore.
Does someone here know what it is or where in the documentation it is?
The documentation used to say something about it changing to 10 minutes in Ignition 8.0 from 7.9
There’s no concept of ‘scan frequency’ in 7.9, because the only ‘source of truth’ for project resources is the gateway’s internal DB.
In 8.0, when resources moved to the filesystem, we put a system in place to watch the filesystem for changes to resources; if an external change is made, it’ll be detected and override the configuration the gateway has in memory. However, the scan frequency was fairly aggressive and could, on systems with many projects, consume a significant chunk of CPU.
As a result, in 8.1 , we lowered the time to scan from a hardcoded default 10 seconds to a configurable 5 minute default rate. The ignition.conf parameter to change is -Dignition.projects.scanFrequency=10: 8.0 to 8.1 Upgrade Guide - Ignition User Manual 8.1 - Ignition Documentation
1 Like
kgamble
December 14, 2021, 10:42pm
3
Ahh it was in the 8.1 doc! I was thinking it came in 8.0 so I was looking in the wrong place.
May be good to add it to this page in the documentation as well:
https://docs.inductiveautomation.com/display/DOC81/Gateway+Configuration+File+Reference
Nit-pick: it was never hardcoded, that system property has always existed.
2 Likes
TIL. Guess that makes sense, I just assumed for some reason it came in with 8.1.
kgamble
December 14, 2021, 11:19pm
6
Out of curiousity, does that technically mean this config option would exist in 8.0 as well?
Yes, it just has a much faster default value in 8.0.
1 Like
kgamble
December 15, 2021, 3:40pm
8
Can't find explicit documentation around automatic project scan frequency in 8.3, but looking like it isn't a thing anymore?
ah, found it mentioned here for reference:
8.3 drops automatic scanning entirely. If you want it to happen automatically, you can set up a gateway timer script somewhere and call system.project.requestScan(), but the better pattern is to fire it whenever git actually needs it to happen, instead of burning CPU cycles scanning unchanged resource trees.
2 Likes