-
Notifications
You must be signed in to change notification settings - Fork 279
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
Revert "Do not enter vendor SAI critical section for counter polling/clearing operations (#1450)" #1498
base: master
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Please give detailed explanation why this is reverted, since previously we established that this indeed helped with stat performance. |
yes, will do |
There is a timeout between SAI and SDK when counters are polled in bulk mode. the timeout is estimated based on the fact that all SAI API calls from syncd's main thread or counter-polling threads wouldn't execute parallelly. |
Which timeout to extend ? Syncd heavy use is only on boot scenario, when you see timeouts why pooling countes? |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
since you touched previously not covered code, you will need to add unittests for this code to satisfy code coverage |
Yes. I did. actually all lines were covered but somehow coverage reported they were uncovered |
doyou have them written in unittests/syncd/TestVendorSai.cpp ? and actually calling those stats ? |
not really but I've reviewed existing test cases and understood the APIs have been covered
Looking at stack frame # 6, clearStats is called. It does not show off in the backtrace maybe because of optimization.
|
For
Stack frame # 6
|
…clearing operations (sonic-net#1450)" This reverts commit 0317b16.
8502955
to
89cf731
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Interesting, but codecovrrage not sure. It's if its optimized, maybe you found a bug in codecoverage |
Revert "Do not enter vendor SAI critical section for counter polling/clearing operations (#1450)"
This reverts commit 0317b16.