iRules vs Policies for Pool Selection?

Thanks for the feedback guys.

The iRule I've written is intended to perform dynamic pool selection based on the URI path and it works pretty slick without being complex (it's just a simple switch with 4 cases).

The alternative that I've tested an verified with an LTM policy is doing a first match on the URI path, and a corresponding rule for each pool, but based on the testing I've done so far I don't see any real performance difference.

When it comes to doing something a little more in depth (like doing a stream iRule with find/replace functionality) I would imaging based on the amount of traffic hitting that virtual server, that the 'penalty' would be a little more significant.