> But this is a daemon that notices changes in user prefs files in real time
so
> the performance issue is spurious. It's _already_ taking a performances
hit
> _every single time_ for every single user.
No. For several reasons.
1) Usually user rules are disallowed. So all SA has to do is open one file
and parse a realtively few lines, which don't include rules. It then
overlays scores on the existing pre-parsed rules.
2) Rules live in many files, like 50s or hundreds of them. These files do
NOT get reread for every user. These are the files that have to be reread
to rebuild the rules after a change.
3) The user rules 'files' in many cases are actually database entries, so
there are no files to open in the first place.
Going out and checking the timestamps on 100 or 200 rules files for every
user would be considerably more overhead than checking the timestamp on one
file, and probably more overhead than opening and reading that one small
file.
Now, checking *occasionally* might not be a bad idea. Where "occasionally"
was maybe once every few minutes or every few hundred mail messages,
depending on the traffic level at a site. Event this could of course be the
wrong thing to do, so there would probably need to be an option to enable
this mode. I'm not at all sure what the appropriate default setting for
this option should be.
Loren
