You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What this service does is basically grab its own pprof info and write it to clickhouse. The heap memory flamegraph data that I download either manually or from the service itself doesn't feel very accurate. emm.. a lot of untime.doInit?
Without knowing what your program does or how it's written, it's hard to tell what an in use heap profile should look like.
Here it looks pretty normal, maybe taken near startup without a lot of application code using memory, with the space eventually attributed to user code.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What this service does is basically grab its own pprof info and write it to clickhouse. The heap memory flamegraph data that I download either manually or from the service itself doesn't feel very accurate. emm.. a lot of
untime.doInit
?What did you expect to see?
Hierarchical heap pprof flamegraph
What did you see instead?
This is the pprof heap file.
heap.gz
The text was updated successfully, but these errors were encountered: