Ok, so here is my understanding. At the very least, every 24 hours, a client will re-evaluate relevance on all Fixlets, Tasks, and Baselines.
Currently, (with the exception of my Portuguese installs), this means that my clients are evaluating 5951 Fixlets every 24 hours.
Out of these 5951 Fixlets, only 1128 of these have one, or more computers that have stated that these are relevant.
So, this leaves me with 4823 Fixlets that are re-evaluated every day for no reason.
If I remove these, won’t they just come back?
One of my thoughts - (if I can remove them from the fixlets) is to put them in a baseline that has a relevance clause in it that says - if you used one of our client image versions that is X version or older, then you need to evaluate all the components, and run this baseline. This would in effect allow older computers to be able to evaluate these fixlets if necessary, but newer computers would skip them.
It is very likely that they are evaluated more than once a day… but the Agent is smart enough to skip all sorts of things that it doesn’t need using several optimizations… For instance:
if the OS doesn’t match the Fixlet, the agent “sidelines” that Fixlet and doesn’t evaluate it again.
for things like file checks, the agent is smart enough not to recheck files if they haven’t changed since the last time it checked.
if the agent doesn’t match the language or OS of a Fixlet site, it can ignore the site altogether.
So the short answer is that we have optimizations in the agent that do things that are very similar to what you are asking for with no work required on your side. This is why the agent can do hundreds of checks a second even with minimal CPU and resources.
There is no way for you to manually muck with which Fixlets to tell the agent which ones to evaluate (other than using “site subscriptions” in the manage sites part of the console).