The local content filtering database does neither affect (ICMP) ping times nor download speed. What it does affect is the time a HTTP request takes, which should improve rendering time for websites with lots of elements.
no kind of web or mail scanning is going to be penalty free...so yes there will always be a speed hit. The 8.3 http proxy though has an additional performance problem. Some kind of performance hit is normal..but 30% or more(again depending on various factors like hardware, traffic type and levels..etc etc etc) is not usually normal..note the word usually.
Running an ASG220 on v8.3 I just tried the steps described here in this thread. The latency was about 200ms higher with web filtering turned on and the speeds are about 30% lower compared to no filtering. After setting the db to be stored on local disk (didn't want to risk running into issues with the 1GB of memory, that is currently 40% used) I don't see any improvement. I pretty much get the same results. I've restarted the http proxy of course and the DB is downloaded and shows 380MB.
Any ideas why web filtering is still slowing the ASG down so much?
Can I verify somehow that the locally stored DB is used instead of contacting the Astaro server every time?
Does anyone else use the 'disk' setting? What's your experience?
