More efficient iRule needed

Hi Hoolio,

 

I am already doing the examination of the host header and assigning to a pool. This is the iRule I have above. Or maybe I am misunderstanding? So right now my iRule looks at the host header, and based on that directs it to a pool (while checking availability of the pool members).

 

 

This works!! However, my issue is that it is very inefficient. This especially comes into play with an intranet site where people download docs. When they download a 25MB doc, I am guessing that the inspection of every single packet to determine the pool, is causing latency in the user experience. When I remove the iRule and have a single pool the speed is good. When I put the iRule back, the sluggishness reappears.

 

 

Does this make sense that this would be the case? I thought F5 would inspect each packet regardless of an iRULE. So I was not expecting this and a little stumped.

 

 

Thanks,

 

 

Dbow