You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Nick,
They definitely do address a memory issue in high speed scenarios.
Vermont originally preallocated a static amount of packet instances and additional instances were added when needed. The problem was that these instances were not freed anymore.
With our changes the preallocated amount of packet instances is configurable (they will never bee freed), and additionally added instances are freed again after use.
The idea is that now the memory usage will always shrink back to the initial size (of preallocated packets instances).
We found that, especially in high speed scenarios, it is advantageous to allocated a higher number of instances at startup, so no allocation operations have to be done during peak situations.
When VERMONT keeps running in packet processing mode, memory consumption will significantly increase over time.
Probable causes:
The text was updated successfully, but these errors were encountered: