-
Notifications
You must be signed in to change notification settings - Fork 22
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
Increased memory footprint #841
Comments
@zolug |
@glazychev-art |
Works as intended. |
@zolug |
Yes, thanks for the quick fix. |
…k-vpp@main PR link: networkservicemesh/sdk-vpp#841 Commit: 5b27c2f Author: Network Service Mesh Bot Date: 2024-08-08 05:10:25 -0500 Message: - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#841) PR link: networkservicemesh/sdk-kernel#671 Commit: c7b682d Author: Network Service Mesh Bot Date: 2024-08-08 05:06:17 -0500 Message: - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#671) PR link: networkservicemesh/sdk#1650 Commit: 3016313 Author: Nikita Skrynnik Date: 2024-08-08 21:03:55 +1100 Message: - Add a timeout for Closes in begin.Server (#1650) * fix corner cases of the begin chain element * disable Test_RestartDuringRefresh * add fresh context * add extended context * add refreshed close context everywhere in begin * fix some unit tests * unskip some tests * fix golang linter issues * debug * cleanup * fix race condition * add unit tests * fix go linter issues * fix race conditiong * apply review comments --------- Signed-off-by: denis-tingaikin <[email protected]> Signed-off-by: NikitaSkrynnik <[email protected]> Signed-off-by: NSMBot <[email protected]>
When running in AF_PACKET mode there seems to be a memory increase in the NSM supplied VPP process on NSM 1.8.
For me it seems the root cause might be the amount of memory assigned to an af_packet socket.
Previously it was ~20MB per socket while with 1.8 it appears to be 135MB per af_packet socket.
In case multiple interfaces are provided in the device-selector-file for vpp-forwarder, vpp seems to create an af_packet socket for each, which can significantly increase the memory footprint (RssFile) and risk OOM.
Is the increase due to the vpp version update? Are there any known NSM issues that are meant to be fixed by the increased af_packet memory?
Might be similar/related to: #332
NSM 1.8.0
Before:
The text was updated successfully, but these errors were encountered: