caching won't hinder performance but if you have any kind of decent bandwidth it's not going to help any. I have one client on sub megabit dsl and i have caching on..but the hit rate isn't that high mainly due to the fact most websites are generated on the fly with little or no static content. If the content isn't static the proxy can't cache effectively.
Actually caching can hinder overall performance in high i/o load circumstances. As William mentions, the usefulness of caching is limited when dealing with dynamic web content.
Try using your QoS. Use more of the DSCP than Best Effort if possible (CS1-CS7), unless you have devices that cannot apply of understand DSCP. Once you separate your traffic, you will see the difference with web caching.
not really..web caching is going to depend on more if he access static content or not.....QOS only controls the rate of various protocols not what is or isn't cached.
Like Bruce and William, in general, I like to leave it off. Sites with a lot of updates can benefit from it, but I prefer for them to use WSUS or comparable tools to distribute updates to internal clients.
I have a client that is a multi-brand "Auto-Mall" where the sales reps all access the same training videos, so I have caching on there. I haven't tried to see if the vids are cached because they're single files, or if they're not cached because they are all streaming media.
it depends if they are truly real time streaming or static files sent a bit at a time. ON twit.tv the videos you can watch after that live shows can be cached as they are actually static files but the live stream itself cnanot be cached as there's nothing static to cache.
Ok, so I might be late, but I definitely need to reply.
So, I think it does since the algorithms are not configurable to the ram size or hard drive size. When I turned it on, my browsing slowed down quite a bit. I'm running this in VMWare ESXi 5.5 with 12 GB of ram, so it performs well overall. When the clients have to use caching, however, latency is introduced.
Just to add, I have to clarify because it may not be the web cache. So when I use transparent mode and web caching, the browser runs slower (I believe it runs slower because it must figure out where the packets come from to pass through), so I made a generic proxy from port 80 and 53 to the web proxy port. Runs twice as fast now!!
Just to add, I have to clarify because it may not be the web cache. So when I use transparent mode and web caching, the browser runs slower (I believe it runs slower because it must figure out where the packets come from to pass through), so I made a generic proxy from port 80 and 53 to the web proxy port. Runs twice as fast now!!
Can you elaborate on how you configured the generic proxy? Is the traffic just going out via the generic proxy or do you have it redirected to the web filtering somehow?
