bugzilla-daemon at bugzilla
Jul 30, 2013, 12:08 PM
Post #2 of 3
(28 views)
Permalink
|
|
[Bug 6963] Anybody cares for a saved millisecond or two in computing bayes probabilities for tokens?
[In reply to]
|
|
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6963
--- Comment #2 from Mark Martinec <Mark.Martinec [at] ijs> ---
Created attachment 5164
--> https://issues.apache.org/SpamAssassin/attachment.cgi?id=5164&action=edit
The scattergram showing the drop in timing
The attached diagram shows elapsed times for computing bayes probabilities
for all messages passing through our server today during a day.
The x-axis is a time of the day in hours (morning to evening),
and the y-axis is elapsed time in milliseconds for each message,
as reported in the 'b_comp_prob' timing log entry.
At around 14:20 the original code was replaced by the optimized code,
which explains the drop in timing. The scattergram is bi-modal,
messages with just few tokens found in a bayes database are almost
unaffected by the change, just a tiny drop is perceived.
The cluster of typical larger messages show about 1.2 ms of
elapsed time reduction.
--
You are receiving this mail because:
You are the assignee for the bug.
|
