iRule + profiles driving up resources

Or you could squeeze out a few more cycles by disabling HTTP_REQUEST for matching IP addresses (assuming you don't have any other iRules running on the virtual server that use the HTTP_REQUEST event):

 

 

when CLIENT_ACCEPTED {

    Only check once per TCP connection if the client IP is part of the datagroup
   if { not [matchclass [IP::client_addr] equals Pilot_Subnets] } {

       Assign the standard pool now and prevent HTTP_REQUEST code from running
      pool HTTP-PROXY_80 
      event HTTP_REQUEST disable
   }
}
when HTTP_REQUEST {

    This code only gets executed if the client IP was in the datagroup
   if { [HTTP::header "User-Agent"] contains "mozycorp-windows/1.8" } {
      pool HTTP-PROXY_80 member 3.56.142.241 80
   } else {
      pool HTTP-PROXY-IRONPORT
   }
}

 

 

Aaron