Adding irules to vip that loop over DGL that are normally empty - ok practise ?

Nitass

 

Sorry I should have phrased my question better. I'm not looking to eval the performance of the irule itself. Obviously, looping over a dgl with actual content will burn up more cycles than an empty one.

 

What I'm looking for is the difference on the virtual server side between executing an irule that essentially does nothing but examine a dgl (to find that it's empty) and not executing the irule in the first place.

 

Most of my vs have the following 5 standard irules:

 

 

filter_http_methods

 

short_to_fqdn_https

 

filter_ciphers

 

redirect_uri_https

 

log_persistence_cookie

 

check_maintenance

 

 

The first 3 rules loop over dgl that always have content. The last 2 irules, however, loop over dgl that are normally empty since on a regular day I don't need to debug persistence nor is the app in maintenance mode.

 

I'm wondering if this vs would burn significantly less cycles if I removed the last 2 irules. The only stats I can find for a vs are 5sec/1min/5min min load average but that's all 0% so would not see a difference.

 

 

I guess the real question is : How many cpu cycles does a virtual server burn when it execs an irule that looks at an empty dgl ?

 

I assume the actual "looping" process never really starts since the group has nothing to loop over so I'm probably worrying over nothing but I wanted to check anyway.

 

I'm simply worried that executing an irule alone burns more cpu cycles than I'd like.

 

 

I hope this is clearer.

 

Thx