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

added thread count to runtime stats. go never closes OS threads once opened, see: https://github.com/golang/go/issues/14592 #250

Merged
merged 1 commit into from
Jun 8, 2022

Conversation

simonmittag
Copy link
Owner

No description provided.

@sonarcloud
Copy link

sonarcloud bot commented Jun 8, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@simonmittag simonmittag self-assigned this Jun 8, 2022
Copy link
Collaborator

@MayankGandhe MayankGandhe left a comment

Choose a reason for hiding this comment

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

I was keen in knowing if we are limiting the number of resources for the non-functional requirements like profiling the performance ,
which basically means that profiling does not consume more resources than it should

@simonmittag
Copy link
Owner Author

I was keen in knowing if we are limiting the number of resources for the non-functional requirements like profiling the performance , which basically means that profiling does not consume more resources than it should

The OSStats updater goroutine runs once a minute to limit the amount of OS resources consumed

@simonmittag simonmittag merged commit 577177f into master Jun 8, 2022
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.

2 participants