Skip to content

ASP.NET Core: CPU Pegged at 100% #306

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.

Sign up for GitHub

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

Jump to bottom
Closed
commonsensesoftware opened this issue Jun 6, 2018 · 1 comment
Closed

ASP.NET Core: CPU Pegged at 100% #306

commonsensesoftware opened this issue Jun 6, 2018 · 1 comment
Assignees
@commonsensesoftware
Labels
asp.net core bug

Comments

@commonsensesoftware
Copy link
Collaborator

Symptoms

After a non-deterministic amount of time and/or load, CPU utilization spikes and seemingly remains pegged at 100%.

Triage

After capturing and reviewing ETL rundowns of the host process, this appears to be caused by runtime manipulation of non-concurrent dictionaries.
@commonsensesoftware commonsensesoftware self-assigned this Jun 6, 2018
@commonsensesoftware
Copy link
Collaborator Author

Recommendation

Upon further investigation and dicussion, API information should be pre-aggregated and placed in dictionaries during startup such that runtime manipulation is not required.

@commonsensesoftware commonsensesoftware mentioned this issue Jun 6, 2018
Merged
@commonsensesoftware commonsensesoftware mentioned this issue Jun 15, 2018
Closed
@commonsensesoftware commonsensesoftware mentioned this issue Jul 31, 2018
Closed
@commonsensesoftware commonsensesoftware mentioned this issue Oct 25, 2018
Closed
@commonsensesoftware commonsensesoftware mentioned this issue Dec 14, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@commonsensesoftware commonsensesoftware

Labels
asp.net core bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@commonsensesoftware