Unexpected TMOS utalsiation hit

The timing command is used to calculate the CPU cycles required to run the iRule. That data is used to extrapolate how many evaluations of the rule can be done for the platform. As far as I'm aware, timing doesn't take into account any other resource requirements. Unfortunately, there isn't a simple way to determine how many TMM CPU cycles other activities are using. So I'm not sure that your scenario shows that the iRule timing is broken. And I don't think there is a linear relationship between the requests per second and the CPU usage.

 

 

There is definitely something odd going on, but I think it's a bit early to say exactly where the problem is. I'll try to keep in touch with Chris on this to see how the troubleshooting progresses.

 

 

Aaron