Forum Discussion
Christian_Gebau
Nimbostratus
NimbostratusiRule optimization / CPU usage monitor
Hi,
I am currently evaluating a BIG-IP load balancer. My goal is to
distribute incoming UDP packets (which conform to a custom network
protocol) to a cluster of linux servers. I use the round-...
Christian_GebauNimbostratus
NimbostratusHi,
we are using "BIG-IP 9.2.3 Build 34.4"
The reason for storing the current time stamp in the map with the sequence numbers is that we have to remove obsolete items from this map at some point in time. Its not possible to detect the end of a session/connection by parsing the content of the UDP packets so we have to rely on removing entries after some timeout. We plan to do this cleanup in a different iRule (because the timer event is not yet available)
I removed the list/timestamp code and did a test. If I just store the sequence number the rule uses an average of 32600 cpu cycles. This is not much lower than the value for the original rule (35500 cycles). The worst offenders seem to be the two commands for reading and writing the UDP payload. A rule that just contains the "binary scan" and "payload replace" commands uses 21300 cycles.
Best Regards,
Christian
pirustihow do you manage to get those numbers, i mean how do you measure the cpu cycles that an iRules uses.
