Unexpected TMOS utalsiation hit

I tested on a 6400 running 9.4.8. I didn't test to a pool. All my requests hit the catch statement for the non-existent pool condition. I was focusing on the iRule operation as opposed to load balancing. I guess there could be something horrible happening with the SSL negotiations or serverside connections, but I've never seen something like that use so many CPU cycles.

 

 

I actually work as a consultant for the partner you're working with. I talked with Chris about the case earlier this evening. The issue is a bit of a gray area between support and sizing/performance tuning. You might try going back to the support group on this. I can talk with Chris and give him some tips for troubleshooting with you.

 

 

Thanks,

 

Aaron