Forum Discussion
Jai_Macker_3993
Dec 05, 2008Nimbostratus
We added the session cookie and this did help a lot with cpu usage now down to around 30% during peak periods. So, the major immediate issue is resolved and thanks to everyone for their help with that.
However, as Colin said, the iRule is still pretty intensive, so I would like to improve that further so it is not an issue again down the road. I added the "timing on" flag before and after the session cookie change and that gave us a 4x improvement, but from this: http://devcentral.f5.com/Default.aspx?tabid=53&forumid=5&tpage=1&view=topic&postid=3650 I can tell that the iRule evaluation is still using up 20% of cpu at 200 req/sec.
For further debugging, is there a way to use the "timing on" for specific blocks of code within an iRule event or can it just be turned on at the global and event level? I'm pretty much wondering if we can get more detailed info on the current execution of the rule with bigpipe before going into the trial and error stage, ie take out the for loops, reset stats and recheck the avg cpu cycles to see their effect, then move on to the next block of code and repeat.
Thanks,
Jai