> >I used to have problems with bayes locking and journaling. When it > >finally corrupted the database, I decided it was time to put > it into a > >real SQL database instead of using DB_File. Haven't had a > single problem > >with bayes CPU or locking since. > > > >Maybe it's time you consider using MySQL? > > > >Bret > > > > > > > > Well, if it solves the problem I'm ready to try almost anything. :) > The way you put your words tells me that the problem IS a > corrupt database. > Can we be certain? And is there any way fo fix it until I can > get MySQL up 'n running?
If the database is corrupted, it should say so. In my case, it wouldn't expire, learn, sync, or use the db_file database because it ended up corrupted somehow. I could have restored it from backup, but chose to simply delete it and start over with SQL. I don't know for sure that this will solve your problem. Bayes still has to tokenize the message, so there is a certain amount of CPU-intensive operations that must happen. Overall, it just seems a lot more stable using a SQL database. I'm using MSSQL here because I have it and it works. Haven't had a single bayes-related problem since switching to SQL. Used to have them very often, sometimes daily. Are you sure you have enough RAM to handle the number of threads you are running? Bret
