Theo Van Dinter wrote:
I'm mostly just venting, but I have 2 machines trying to do the
scoregen run, so I need to share the Bayes DB, and chose SQL. In total
across those machines, I'm currently only seeing ~25 msgs/min or 0.5
messages/sec. So for my ~215k messages, that's 430k seconds, or 5 days
of processing. Set 1 would take ~12h for this same set of messages,
so bayes adds a 10x time penalty?
Am I missing something? MySQL w/ InnoDB + and BayesStore::MySQL, MySQL 4.1.
Granted, I haven't timed this against SDBM or DBM, but I'll take any hints
for MySQL tuning. An upside of using the mass-check client/server code
is the ability to stop the clients, change MySQL configs, and restart
the clients, and not lose the previous work. :)
Thia all sounds a lot like mine which is doing the bayes through SDBM.
It is now just over 50% done and looking like it is going to run for a
couple more days. I didn't know it was possible to use MySQL for the
scoregen runs. I would have used it instead. I also should have used a
smaller corpus.
The machine I am running mine on is a 1.8Ghz with 1.5Gigs of RAM. Only
seems to swap when some of the heavier cron events run. I should have
used a different machine.
How do you see how many msgs/min it is processing? Be aware I'm running
on my first cuppa coffee. 8*)
--
-Doc
SA/SARE/URIBL/SURBL -- Ninja
8:20am up 16 days, 17:18, 15 users, load average: 3.73, 2.45, 2.19
SARE HQ http://www.rulesemporium.com/
