NimbostratusI just wanted to know in general , when to use the http compression , wan optimized compression and when to use web acceleration-optimized caching and optimized acceleration ? Suppose we have a scenario , where the fetching of web page takes more than the time expected while going via F5 , what profile can help me with this scenario ?
CirrocumulusThe best way to see if there is any improvement is to test traffic with that profile.
Firstly, you have multiple TCP profiles, so you can test that based in the type of connection and device you have in the client side and server side.
Next is HTTP related profiles, you talked about compression and caching.
Compression would make the pages smaller, so fast to transfer, but needs to be decompressed in the browser, so it may not improve things.
Caching, will remove some work from the server, and also provide faster response to the client. However, that requires more RAM memory F5 device, or disk in case you go for AAM.
So the answer is not easy, as it depends on your requirements/scenario. However, with caching you should definitely see some improvements.