Skip to content
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

[counters]: separate query of port/queue counters #483

Merged
merged 1 commit into from
Apr 24, 2018

Conversation

sihuihan88
Copy link
Contributor

Signed-off-by: Sihui Han [email protected]

What I did
Separate port and queue query. By default query port counters every 1s, and queue counters every 10s
Why I did it
Querying all queue counters every 1s is cpu consuming. Reducing queue counter query rate helps to reduce cpu overhead.
How I verified it
Tested on DUT.
Details if related

@@ -34,8 +34,10 @@ extern CrmOrch *gCrmOrch;

#define VLAN_PREFIX "Vlan"
#define DEFAULT_VLAN_ID 1
#define FLEX_STAT_COUNTER_POLL_MSECS "1000"
#define STAT_COUNTER_FLEX_COUNTER_GROUP "STAT_COUNTER"
#define PORT_FLEX_STAT_COUNTER_POLL_MSECS "1000"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are both polling intervals controlled by cli or through fields in config_db.json?
If yes, can you please tell me how?

If not, then those intervals need to have more control.

Copy link
Contributor

@nikos-github nikos-github Apr 22, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also queue counters polling must not be enabled by default.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Nikos-Li , please create feature request in the issue, we'll triage later.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lguohan This isn't a feature request, nor a proper solution to the CPU increase we have observed. This needs to be discussed in the 3-way meeting. Please include it in the agenda.

Copy link
Contributor

@nikos-github nikos-github Apr 22, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lguohan @sihuihan88 Please also provide CPU util data of before and after and a proper root cause analysis as well as the testing done, verification etc. None of this exists in the PR and an almost 200% increase in CPU util, makes this a critical fix.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lguohan @sihuihan88 Do not merge this without proper RCA and explicit approval and discussion in the 3-way meeting.

Copy link
Contributor

@nikos-github nikos-github left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lguohan We need to discuss this.

@lguohan lguohan merged commit 4a26e15 into sonic-net:master Apr 24, 2018
lguohan pushed a commit that referenced this pull request Apr 25, 2018
@sihuihan88 sihuihan88 deleted the dev/sihan/counter branch April 25, 2018 19:54
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
oleksandrivantsiv pushed a commit to oleksandrivantsiv/sonic-swss that referenced this pull request Mar 1, 2023
oleksandrivantsiv pushed a commit to oleksandrivantsiv/sonic-swss that referenced this pull request Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants