Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory consumption increases heavily over time #10

Open
constcast opened this issue Mar 16, 2012 · 2 comments
Open

Memory consumption increases heavily over time #10

constcast opened this issue Mar 16, 2012 · 2 comments

Comments

@constcast
Copy link
Contributor

When VERMONT keeps running in packet processing mode, memory consumption will significantly increase over time.

Probable causes:

  • The InstanceManager will allocate new Packets at peak times which will never be freed (check by disabling the Manager)
  • FlowHashtable filling up
@nickbroon
Copy link
Contributor

nickbroon commented Nov 29, 2018

@felixe
Copy link

felixe commented Nov 29, 2018

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.

hope that helps,
best

felix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants