I am having a problem with our Web Gateways. 184.108.40.206
After big downloads, around 600MB, the scanning process takes over an hour to complete. The CPU stays around 60 - 70% the whole time.
Anyone else having this problem with large downloads? It takes longer to scan than it does to download...this can't be right. 600 MB is not even that big now a days.
3451 seconds = around 58 mins.
this is just a matter of what you are downloading! If it is a file that contains other nested files and archives, MWG will scan every one of them. This can be lengthy, depending on size of the file. The CPU utilization simply comes from the fact that scanning operations are CPU intesive. As workaround you set a barrier at a certain file size to not scan the file if above this size and let them through.
it is difficult to answer where to put the Rule set without knowing the whole Policy. Based on the Default Ruleset I would try to apply the rule as in the below screenshot (see the first rule):
Should basically work, have not tried it for the moment.
This seems to be working. If the file is over 8mb it just downloads with the browser download box. If it is under 8mb, the Gateway progress page is displayed and the file is scanned.