Hi, We noticed a big increase in user CPU utilization on our MX servers since Sep 2nd sa-update. On a typical day we process over 2 million emails on our mail cluster. Our debugging has so far isolated the problem to:
1) iXhash was a problem module , so we disabled it (the remote location it was hitting was causing a problem) 2) The following RBLs spamhaus, mailspke, njabl, spameating monkey, were determined to be causing latency with dig@localhost queries, so they were removed 3) dcc, pyzor and razor2 and freewebmail were disabled 4) sa-compile was utilized to improve the systems being cpu bound We have tested by turning the following flags on (to disable the services): $skip_rbl_checks= 1 (spamassassin) $sa_local_tests_only = 1 (amavis hook) With the above we have started to see an improvement but we are still trying to identify the root cause. Our current fix is really a patch since those custom changes will be removed during the next nightly sa-update run. Are there recommend ways to create an exclude list to allow these types of local updates to be included in the sa-update workflow without having to hack it directly? Has anyone experienced anything similar since September 2nd update? -- Piotr Kapiszewski
