How hard is it to keep list mail on list and not reply directly to sender?
Have you seen
https://svn.apache.org/repos/asf/spamassassin/trunk/contrib/HOWTO.Bayes-Redis/
?
there may be some helpful info in there.
On 4/16/21 9:47 AM, Christian Völker wrote:
Thanks for the hint. I will monitor it. The machine has 16GB of memory
which should be sufficient but I already notivce the preallocation of
redis with 2GB.
It is somehow unclear what happens. If there is no limit I will get an
OOM errror and redis will (if killed) loose the last transactions after
the last "save 900 1" snapshot, right?
If I set a limit it will discard the oldest entries, correct?
Both seems not to be perfect for Spamassassin.
However, I will ignore the topic for the moment and see how it goes.
16GB shoud (hopefully) be enough. Once scanned the expired rules of
Spamassassin should take place and reduce the amount of memory.
Greetings
/Christian
Am 16.04.2021 um 09:15 schrieb Axb:
To avoid suprises, remember to watch your memory usage.
Redis reads/writes the DB in memory and only dumps to disk for backup.
"redis-cli info" is of help
On 4/16/21 9:10 AM, Christian Völker wrote:
Sorry to annoy you. Another addition to my tests:
When using redis it took me around 15seconds to scan ~1,500 messages.
When using MariaDB it took one minute to do the same.
With file based I had strange issues whatever lock type eI used
(flock yes/no):
"bayes: bayes db version 0 is not able to be used, aborting! at
/usr/share/perl5/Mail/SpamAssassin/BayesStore/DBM.pm line 206."
Anyways, now using Redis which appears to be the fastest.
Thanks again!
/Christian
Am 16.04.2021 um 08:48 schrieb Christian Völker:
Hi,
So I will re-configure my installation to use MariaDB.
You should also consider the Redis backend.
Ok, had a look when using MariaDB and I monitored it for the last
24hrs. My 10 vCPUs where used, no I/O waits. But CPU usage overall
was according to "top" only at 25% as top showed 75% idle. I assume
there is some locking in place limiting the CPU usage.
I configured it now to use Redis instead of MySQL and top tells me
about 25% idle with 0% I/O waits when running 10 sa-learn in
parallel. Increasing or decreasing the number of jobs does not
significally change the idle percentage.
So using redis the CPU usage is higher compared to MySQL.
Thanks for ideas!
/Christian
