-
Notifications
You must be signed in to change notification settings - Fork 35
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
NSMgr v1.12.1-rc.1 causes latency spikes at certain traffic level #11372
Comments
In the meantime we repeated the tests with increased CPU resource limit for NSMgr pod and the latency spikes disappeared. It proves that something changed in NSMgr that causes higher CPU need periodically. |
@szvincze |
@glazychev-art, please find the logs attached. |
This was referenced Mar 22, 2024
This was referenced Mar 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Question
Were there any modification in NSMgr between v1.11.2 and v1.12.1-rc.1 that can cause latency spikes?
Examples
In NSM v1.11.2 and before we managed to run traffic up to 30k TPS without spikes in latency, but with v1.12.1-rc.1 we observed significant latency spikes (up to 5 seconds) that caused disturbances and even disconnection of the SCTP peers.
To exclude the different NSM components we tried to run the same test with the previous release that worked well but added the components from the new RC one by one. When we used the forwarder-vpp from the RC and the other components from 1.11.2 the setup worked as expected, without latency spikes. The new forwarder-vpp and new registry-k8s combination also performed well, but when we added the NSMgr from the RC the latency spikes appeared.
So, it seems the NSMgr component has influence on this behavior.
Important to note that the mentioned latency spikes come periodically, in every two minutes, and this behavior starts when we reach 15k TPS traffic level.
Context
The text was updated successfully, but these errors were encountered: