[Bug 3986] New: add init_learner() flag to limit opportunistic work

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3986

           Summary: add init_learner() flag to limit opportunistic work
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Learner
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: felicity@kluge.net


Per discussion at ApacheCon, I'd like opportunistic calls to remain working the
same way as today, except that when a certain flag is set (init_learner() is the
usual method) only checks will be done -- I figure we can update the
PerMsgStatus object to indicate whether expiry or sync is required.

The idea is that for things like spamd, we should have the processing children
do the message processing, return the message, and go back waiting for a new
message as quickly as possible.  Things like Bayes expiry occur before the
message is returned, and can cause the child to be busy for several minutes.

I looked into doing this already, but found several issues such as no
PerMsgStatus object being available in the opportunistic area, and opportunistic
sync being called in various places such as "is_scan_available" (which occurs
because a journal sync may push the # of ham/spam over the limit, thereby making
Bayes available for scanning).

I don't actually think a journal sync is very length, so this could even just be
for expiry only.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.