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

[Question] - How to indentify the cause of high CPU usage within a Service Fabric application #1504

Open
brewstertimothybrewster opened this issue Jul 18, 2024 · 1 comment
Labels
type-code-defect Something isn't working

Comments

@brewstertimothybrewster
Copy link

brewstertimothybrewster commented Jul 18, 2024

Since a few months we see a steady increase in average CPU usage within our Service Fabric cluster.
It started from the 24th of April with a average CPU usage of 29% until the 11th of Juli with a average CPU usage of 80%.

After loggin in to one of the nodes within the cluster, we saw that one of the three Service Fabric applications was consuming alot CPU ranging from 40-90%.
image

The 11th of Juli we deleted the Service Fabric Application and redeployed it which decreased the average CPU usage to 16%.
But after that the CPU started slowly rising again, at this moment the average CPU usage is 20%.

I tried to investigate this with the Visual Studio diagnostic tools, but the tools are not supported for Service Fabric applications it seems.
My question is what are the options/possibillities to investigate this, to find out where the CPU increase is comming from.

Service Fabric Runtime Version:
10.1.2175.9590

Environment:

  • Azure
  • OS: Windows Server 2022 Datacenter
  • Version Latest
@brewstertimothybrewster brewstertimothybrewster added the type-code-defect Something isn't working label Jul 18, 2024
@GitTorre
Copy link
Member

SF services are console apps. In VS cpu diagnostics tool, you simply connect to the service process. So, on your dev machine, launch your SF application from VS, then connect to the target service process and start the analysis session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-code-defect Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants