[flex-counters] Delay flex counters stats init for faster boot time#1646
[flex-counters] Delay flex counters stats init for faster boot time#1646yxieca merged 7 commits intosonic-net:masterfrom shlomibitton:shlomi_delay_counters_2_master
Conversation
|
@stepanblyschak could u please help to review? |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@shlomibitton please check test failure on PG counters. this is the only test i think relevant to your changes. |
|
/AzurePipleines run |
Signed-off-by: Shlomi Bitton <[email protected]>
Fix 'test_pg_drop' to adapt new change Signed-off-by: Shlomi Bitton <[email protected]>
2960e16
|
@stepanblyschak any comments? |
|
@stepanblyschak kindly please review. your approval is needed for such change. |
| @@ -0,0 +1,83 @@ | |||
| import time | |||
There was a problem hiding this comment.
@shlomibitton could you please provide description of the flows to be tested in this unit test? it will help to ensure all cases are handled as part of the ut
There was a problem hiding this comment.
@liat-grozovik Added the test flow and description to the PR, please review.
|
/azp run |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@judyjoseph and @yxieca would you like to review this PR as well? |
|
@yxieca and @judyjoseph can you please review? |
|
@shlomibitton there are merge conflicts w/ the 202012 branch, please submit a PR against 202012 for this change. |
[flex-counters] Delay flex counters stats init for faster boot time (sonic-net/sonic-swss#1646) [routeorch] Add support for blackhole routes (sonic-net/sonic-swss#1723) Update pool sizes during initialization from timer only (sonic-net/sonic-swss#1708) Signed-off-by: Shlomi Bitton <[email protected]>
|
[flex-counters] Delay flex counters stats init for faster boot time (sonic-net/sonic-swss#1646) [routeorch] Add support for blackhole routes (sonic-net/sonic-swss#1723) Update pool sizes during initialization from timer only (sonic-net/sonic-swss#1708) Signed-off-by: Shlomi Bitton <[email protected]>
[flex-counters] Delay flex counters stats init for faster boot time (sonic-net/sonic-swss#1646) [routeorch] Add support for blackhole routes (sonic-net/sonic-swss#1723) Update pool sizes during initialization from timer only (sonic-net/sonic-swss#1708) Signed-off-by: Shlomi Bitton <[email protected]>
…onic-net#1646) 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.
…t time (sonic-net#1646)" (sonic-net#1743) This reverts commit ee7a735.
…onic-net#1646) 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.
…t time (sonic-net#1646)" (sonic-net#1743) This reverts commit ee7a735.
Signed-off-by: Shlomi Bitton [email protected]
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