Forum Discussion
NimbostratusForecast Impact of MD5 Function in iRule
We'd like to take an md5 of the string clientip+request_uri+clock_clicks on every incoming request. We'll take md5, and append it to the cookie collection. This will not be tracked, i.e., we won't add it to rsp_cookies, we'll just toss it in on request. What I'd like to know is: are there any metrics on doing something like this? I see this as a processor intensive operation, but how much? We can put it on our test F5 but it's hard to mimic live traffic, or determine the affect of a single request to do the proper math. Any thoughts on how we could forecast the impact of something like this?
Thanks!
1 Reply
- Kevin_Stewart
Employee
Check out the timing command:
https://devcentral.f5.com/wiki/iRules.timing.ashx
I'd add this command at the event level and look at the difference in CPU usage with and without the MD5. That'll give you a per-request look at the impact of MD5. If you can control the traffic to the virtual server in the test environment, and can generate a proper load, the "CPU Utilization Avg." under virtual server statistics should also give you a decent idea of the impact with and without MD5.
