Forum Discussion
Luis_Su__225_re
Oct 08, 2013Nimbostratus
Thanks for your answer. Some of the suggestions apply to our site, some don't, but that's the kind of answer I tried to obtain.
I'm sure that most F5 systems are deployed on production by F5 specialists, but they will eventually be managed by the customer systems/operations team. That kind of users (as myself) may find these best practices useful when traffic grows unexpectedly or changes in backend applications require changes on many configurations. So even if your recommendations seem generic and obvious to F5 experts, they are useful and should be reminded from time to time.
Some more tips we've found:
- One connect is very helpful, when managing hundreds of simultaneous connections
- On the WA policy "Queue Parallel Requests" is also very useful to avoid the effects of popular media content, or new applications increasing the number of requests without previous warning.
- Also, on WA policy, "Cache only if the document contains matching begin and end tags" might avoid caching of internal applications' responses.
- Using a large cache is also required most of the times, and the default number of objects on wa profiles (1000) is very low for large sites.
- TCP connection timeouts should be in sync with those of the CDN. If your CDN will disconnect after 120 seconds, you shouldn't have larger timeouts.
- We are not using WA for large files (over 100MB), that would use resources from the F5 system, that can be better used serving and caching small files.
- What_Lies_Bene1Oct 08, 2013CirrostratusThanks Luis, interesting stuff.