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

run golang cpu profile for 5mins but only got 1.64mins (32.69%) samples #39922

Closed
qibobo opened this issue Jun 29, 2020 · 4 comments
Closed

run golang cpu profile for 5mins but only got 1.64mins (32.69%) samples #39922

qibobo opened this issue Jun 29, 2020 · 4 comments

Comments

@qibobo
Copy link

@qibobo qibobo commented Jun 29, 2020

What version of Go are you using (go version)?

$ go version
go version go1.13.10

In the container, the golang process used 100% of the CPU. When I took a 5minutes CPU profile, the result shows that only 1.64mins (32.69%) samples are returned. Is it normal?

go tool pprof autoscaler_cpuprofile.out
File: autoscaler
Type: cpu
Time: Jun 29, 2020 at 11:21pm (CST)
Duration: 5.01mins, Total samples = 1.64mins (32.69%)
@networkimprov
Copy link

@networkimprov networkimprov commented Jun 30, 2020

Some discussion of profiler shortcomings is here:
https://groups.google.com/forum/#!topic/golang-dev/LCJyvL90xv8

@qibobo
Copy link
Author

@qibobo qibobo commented Jun 30, 2020

@networkimprov
Seems the answer you provided is not relevant to my question.

@networkimprov
Copy link

@networkimprov networkimprov commented Jun 30, 2020

This issue tracker is for bug reports and proposals. You'll get more & quicker responses to questions by posting on golang-nuts or golang-dev. I referred you to a discussion where folks would answer your question.

@qibobo
Copy link
Author

@qibobo qibobo commented Jun 30, 2020

@networkimprov thank you.

@qibobo qibobo closed this Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.