[flex-counters] [202012] Delay flex counters stats init for faster boot time #1804
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add flex counters unit-test Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
yxieca
approved these changes
Jul 1, 2021
liat-grozovik
pushed a commit
to sonic-net/sonic-buildimage
that referenced
this pull request
Jul 5, 2021
[flex-counters] [202012] Delay flex counters stats init for faster boot time (sonic-net/sonic-swss#1804) Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com>
qiluo-msft
pushed a commit
to sonic-net/sonic-mgmt
that referenced
this pull request
Aug 16, 2021
…hange (#3903) ### Approach #### What is the motivation for this PR? Following PR's: sonic-net/sonic-swss#1803 sonic-net/sonic-swss#1804 Flex counters are delayed and these tests are failing as a result of missing information on the DUT. This PR is to wait until all counters are enabled before running the test. Timeout value chosen by the delay script which can be found here: https://github.com/Azure/sonic-buildimage/blob/master/dockers/docker-orchagent/enable_counters.py #### How did you do it? Wait until all counters are enabled before running the tests. #### How did you verify/test it? Run the tests with this change.
vmittal-msft
pushed a commit
to vmittal-msft/sonic-mgmt
that referenced
this pull request
Sep 28, 2021
…hange (sonic-net#3903) ### Approach #### What is the motivation for this PR? Following PR's: sonic-net/sonic-swss#1803 sonic-net/sonic-swss#1804 Flex counters are delayed and these tests are failing as a result of missing information on the DUT. This PR is to wait until all counters are enabled before running the test. Timeout value chosen by the delay script which can be found here: https://github.com/Azure/sonic-buildimage/blob/master/dockers/docker-orchagent/enable_counters.py #### How did you do it? Wait until all counters are enabled before running the tests. #### How did you verify/test it? Run the tests with this change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: Shlomi Bitton shlomibi@nvidia.com
What I did
Update flex counters DB with counters stats only when counters are enabled.
As long as the polling counters are not enabled, flex counters information will stored internally on PortsOrch.
Why I did it
Creating flex counters objects on the DB will trigger 'SYNCD' to access the HW for query statistics capabilities.
This HW access takes time and will be better to finish boot before doing this (mainly for fast-reboot but good to have in general).
The flex counters are not crucial at boot time, we can delay it to the end of the boot process.
How I verified it
Reboot a switch and observer the flex counters DB populated after counters are enabled.
Details if related