[action] [PR:16854] Add memory consumption check for bgpd/openbmpd during test_default_route_with_bgp_flap stress test #16859
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Microsoft ADO id: 27588923
Added performance test for bmp feature, since after bmp feature switch is enabled it will introduce some impact into below two processes:
/usr/lib/frr/bgpd -A 127.0.0.1 -P 0 -M snmp -M bmp
/usr/bin/openbmpd -f -l /var/log/openbmpd.log -c /etc/bmp/openbmpd.conf
This PR aims at adding some memory monitoring measurement during test_default_route_with_bgp_flap() execution, given this case will introduce bgp flapping which is under extreme condition, and impact bgpd/openbmpd potentially.
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Add some memory monitoring measurement during test_default_route_with_bgp_flap() execution, given this case will introduce bgp flapping which is under extreme condition, and impact bgpd/openbmpd potentially.
How did you do it?
Before test_default_route_with_bgp_flap() is launched, it will record current memory utilization of bgpd/openbmpd as initial value, during the bgp flapping test execution, there'll be two dedicated threads which check memory utilization every 30s and see if it exceeds two times of initial value and break the test correspondingly.
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation