You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Kasper Sacharias Eenberg <ks...@hovmark.dk> on 2009/06/22 15:57:40 UTC

[Fwd: Re: Bayes and SQL.]

Forwarding this to the mailing list as i failed to set the reply-to
field.

-------- Forwarded Message --------
> From: Paweł Tęcza <pt...@uw.edu.pl>
> To: Kasper Sacharias Eenberg <ks...@hovmark.dk>
> Subject: Re: Bayes and SQL.
> Date: Mon, 22 Jun 2009 15:08:04 +0200
> 
> Kasper Sacharias Eenberg pisze:
> > Thank you for the response.
> 
> No problem :)
> 
> >> Did you try MySQL dumps? It should be faster way for restoring.
> >> 
> >> mysqldump your_bayes_db > bayes_dump.sql
> >> echo "drop database your_bayes_db" |mysql your_bayes_db
> >> echo "create database your_bayes_db" |mysql your_bayes_db
> >> mysql your_bayes_db < bayes_dump.sql
> >> 
> > 
> > I do run MySQL dumps for backups on the server.
> > I was wondering however if it was a symptom that of bad performance,
> > that restoring backups with sa-learn was slow.
> > In essence, i was wondering if it happened to everyone :)
> 
> Unfortunately I don't remember any issues with restoring backups with
> sa-learn. I'm not sure I was doing it at all :D
> 
> If I'm thinking properly your sa-learn runs on client and it needs to
> download/upload Bayes data to your server via network to store/restore
> data base. Maybe you have a lot of data and it's a reason of bad
> performance?
> 
> >> > Versions:
> >> > CentOS 5.3
> >> > Spamassassin 3.2.5
> >> > Perl: 5.8.8
> >> > MySQL: 5.0.45-7.el5  (The mysql is run on another server of WAN)
> >> 
> >> What database storage do you use for your Bayes? I remember that we had
> >> to switch from MyISAM do InnoDB because of stable and performance issues.
> >> 
> > 
> > Currently we are running MyISAM.
> > My understanding is that running InnoDB would create a mass of overhead
> > we don't really need. With all the extra transaction logging going on
> > and what not.
> > But i might try it. I'm not a MySQL guru as you might have figured.
> 
> No, I haven't figured it :) If you're satisfied with MyISAM then you
> should still use it. A rule "Don't touch it if it works well" is good :)
> 
> I was testing both storages and InnoDB was better for me, because it had
> a bit more SELECT statements per second then MyISAM and much more
> INSERTs and DELETEs. MyISAM was a bit better only for UPDATEs.
> 
> But I agree that InnDB is more difficult for maintaince.
> 
> >> Have a nice summer day :)
> > 
> > A nice summer day to you aswell. (The sun is actually shining here for
> > once! :)  )
> 
> You're lucky person! ;) We have cloudy weather here :(
> 
> Cheers,
> 
> P.
>