Hi, this may be a stupid question but as someone from a time where computing power was not that freely available I am wondering if the frequency of running a rule is affecting anything.
Is there a - measurable - amount of higher load to the CPU if I run a rule each minute compared to only once an hour? I am reluctant to check every minute so it has no effects on performance/battery levels.
Any hint on how you run your rules appreciated.
I would like to know that too. I will say my rules run ‘on import’ mostly. I have had ones that run a couple of time a day or on startup. I have never noticed any performance issues at all. I have to say I don’t have any need for a rule, and can’t envisage one, for anything more than once an hour at the most. If there was a limit of once a day, it would be fine for everything I do. As long as I could run a rule on ‘import’ as well. I would like to know the answer though.
I’d say the answer is: it depends on what the smart rule was doing, not that it’s triggering every minute. You could use a Play Sound: Sosumi and other than likely becoming quickly annoying, it wouldn’t swamp your system.
But my question is: Why would you use use the Every Minute event trigger? It’s there as an option but what is the specific reason you’d use it?
My question was mostly out of curiosity. I started to use time triggers sometime in the past when ‚on Import‘ was sometimes not reliable.
My rules only move documents to matching groups.
Understood.
Intervallic event triggers are available to use but I would discourage careless use of them, just to avoid it becoming a habitual option to choose. This could become a danger when applied to a more intensive chain of smart rule actions. I’d say for most intents and purposes, hourly or daily is generally sufficient. I actually have two daily smart rules running for many months now.