> -----Original Message----- > From: David F. Skoll [mailto:d...@roaringpenguin.com] > Sent: Wednesday, August 03, 2011 8:58 PM > To: users@spamassassin.apache.org > Subject: Re: MySQL Bayes - can slow MySql cause other tests not to run? > > > > you may see that the contention per scan lasts at most ~5ms, which is > > ~1/1000 of the above one. > > Except that in real life, the write transaction lasts much longer,
What is it? 60ms? Granted. It is still a 1/100 of 6s. > especially when multiple processes are trying to update the same rows. > (That happens quite often.) That is the effect of the contention for the "holded contenders", which you won't take into account if you are computing how long a transaction lasts. > > It is a matter of facts, however, that I don't know if the > transaction > > boundaries in Mail::SpamAssassin::BayesStore::MySql are like the ones > > I depicted in the previous figure. I don't know exactly the timing of > > the various bayes operators in SA. > > Looking at the code, it seems that the reads and the writes are done > in non-overlapping transactions. Ok. Let me see where in the code you see the transaction is completed soon after the token scores are fetched. Regards, Giampaolo > Regards, > > David.
