There are few reasons for implementing Redis DB for me (my company) may
be not all of it is objective because i like these key value storages.
1) Simplicity - Redis DB is simple to use and to maintain and is much
more complex then other key value storages - remember that first
storages were key value (BDB, etc.).
2) Scaleability - Redis DB is pretty highly scalable, and the purpose of
this plugin is tu use Bayes for high performance nodes. In future there
should be lots of new things about Redis functionality, so I thought,
that i would be nice to give it a try.
3) Resources - i did some short tests about memory consuption and i get
to the 10% or less of memory consuption with comparsion to MySQL
engines. This reason may be odd, i have to make much more tests.
4) Autoexpire - SEEN table is not expiring and this table grows fast. If
you learn your bayes with 50000 emails per day, it grows into pretty big
monster after few years, and there's no mechanism keeping time signature
of seen entries. With Redis DB you can set EXPIRE time of SEEN key (it's
also implemented in this plugin) and you don't have to care about
These are my reasons, but I understand if you rather use simplier way
with MySQL memory engine. The point is that the plugin is almost done so
why not make it better?
Dne 27.3.2012 11:36, Benny Pedersen napsal(a): > Den 2012-03-26 18:26, Jan Hejl skrev:
>> Hello everyone,
>> last few months i've been working on new BayesStore module. This
>> module uses all-in-memory DB called Redis - more at redis.io
> so why not use mysql memory engine ?
> will your plugin store data on shutdown of server ?
Which one will do? >
>> I've put the code on sf.net http://sourceforge.net/projects/bayesredis/
>> It's usable (at least for me) but it's still under high development.
> remove loadplugin in cf files and move this line into pre file
Sorry, this line is deprecated. I use this as you say inside pre files.
Thanks for pointing >
>> I hope that this could be interesting for someone and if you could
>> help me to make it work properly and better I'll be glad.
> here i just try to use mysql with less then 30% ram, its a hard work
> with both bayes, and dspam, but usaly i find what can be scaled down
> in mem usage without make to much collective damage :)