I notice that the --config-test option is painfully slow with a graylist
of any size. I just ran it with a graylist of <5000 entries, and it took
several minutes. It did finally finish fine, so it's not much of a
problem. In comparison, qtp-prune-graylist ran against the same graylist
in 8 seco
| I notice that the --config-test option is painfully slow with a graylist
| of any size. I just ran it with a graylist of <5000 entries, and it took
| several minutes. It did finally finish fine, so it's not much of a
| problem. In comparison, qtp-prune-graylist ran against the same graylist
| in
I'll take a look at the code to see if there's anything wrong, but it's
likely there's not a lot I can do about this (except make the test less
comprehensive). The graylist test looks at every folder and file
individually, examines permissions and tests writeability. Since the
goal is to iden
That what I suspected. Now that you mention it, I did have some write
inefficiencies configured (lacked write caching) that have since been
corrected. I just tested again, and results were much better, more like
what I would expect. I think the writes were what was clobbering
performance.
If y
