Forum Discussion

JoeTheFifth's avatar
JoeTheFifth
Icon for Altostratus rankAltostratus
Nov 03, 2019

iRule Proc and Performance

I started using iRule procs in a very big irule.

I have like 30 procs in this iRule.

I haven't noticed any performance issues in my test lab and in my staging environment.

The procs are mostly called on initial session/connection and then cookies are used to bypass the procs.

DO you guys have any advice as to the use of procs. I find them really powerful and they have helped me have a clean nice iRule to do a lot of stuff in combination with APM.

How are the procs managed in ram when they are not called?

Do they get destroyed when the iRule events close?

Are there any optimization options to minimize memory usage since these procs are loaded whenever the irule is called?

I'm using version 12.1.3.

For the moment I'm keeping all the procs in the same iRule.

 

3 Replies

  • It is generally a good idea to use procs for reusable code. I guess they are compiled in the same way but I would recommend using a full path to specify them to avoid ambiguity. You can also fall foul of the BIG-IP caching the library so development can be a pain.

  • For the moment I use all the procs in a single irule.

    I really need to find out how much memory footprint they will have on a 10-20k concurrent connections.

    • PeteWhite's avatar
      PeteWhite
      Icon for Employee rankEmployee
      They are compiled into bytecode and cached so the number of connections is irrelevant.