Queuing traffic in iRules - advisability!!
I posted this codeshare recently which is a pair of iRules which queue requests in front of WAM with the idea being that when they are released the request will be in cache and served from cache https://devcentral.f5.com/wiki/iRules.Web-Object-Request-queuing-for-WAM-v10-x.ashx, using the entries in the session table as kind of semaphore to signal when a page request was in progress. The purpose of this was to reduce spike load on the backend servers when page objects expire from WAM cache, as the backend system is a CMS for which assembling new pages is relatively CPU-intensive. I haven't deployed this to a production system yet but it's very close to it.
I today stumbled upon a few discussion threads from a few years ago which have alarmed me, to say the least, all saying DON"T do what I have done ie;-
https://devcentral.f5.com/questions/irule-that-waits21872
https://devcentral.f5.com/questions/queue-traffic-after-session-rate-limit-reached
Now, I suspect (hope) that the introduction of command suspension http://support.f5.com/kb/en-us/solutions/public/12000/900/sol12962 will have alleviated some if not all concerns on this front, but I'd like some prompt advice on the topic!!