tests_pri_0 taking a long time, but which rule EXACTLY?

Ralf Hildebrandt Ralf.Hildebrandt at charite.de
Wed May 13 17:32:58 CEST 2015

> 5.289654E+01 FUZZY_CLICK_HERE
> 5.295207E+01 FUZZY_IMPORTANT
> 6.199045E+01 FUZZY_ROLEX
> 6.461184E+01 FUZZY_AMBIEN
> 6.624127E+01 FUZZY_PRICES
> 6.724566E+01 PP_TOO_MUCH_UNICODE05
> 7.878561E+01 FUZZY_ERECT
> 9.233920E+01 MIME_BASE64_BLANKS
> 2.089959E+02 SPF_SOFTFAIL
> 4.875458E+02 SPF_NEUTRAL
> 8.783782E+02 SPF_HELO_NEUTRAL
> 6.531796E+03 DCC_REPUT_13_19
> 1.545746E+04 DCC_CHECK
> 1.316323E+05 TXREP
> As you can see, some check take a magnitude more time.

I found out that a BerkeleyDB based "TXREP" storage is very slow.
Switching to mysql solved that.

Ralf Hildebrandt                   Charite Universitätsmedizin Berlin
ralf.hildebrandt at charite.de        Campus Benjamin Franklin
http://www.charite.de              Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

More information about the amavis-users mailing list