according to the perf report a significant amount of time is spent in runtime.newsstack and runtime.oldstack. pprof does not report this time at all, which explains the missing time in pprof. this is odd.
and: i don't know what causes the program to spent so much time in runtime.newsstack, this behaviour occurred after making a rather small change (saving some values into an array along the way). going back to an old version make pprof and perf report look equal. maybe this information is important, because i can imagine the problem lies deep somewhere in the go runtime code. just guessing.
any help appriciated. regards
heiko
Dmitry Vyukov
unread,
May 22, 2013, 3:23:56 PM5/22/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to golan...@googlegroups.com
Hi,
Thanks!
There is indeed an issue in pprof profiler in Go runtime, it ignores samples in newstack/oldstack.
So what I do right now is turning my recursive function into an iterative one. Seems I end up in spaghetti code this way.
Dmitry Vyukov
unread,
May 23, 2013, 3:26:51 AM5/23/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to hs, golang-nuts
Thanks!
I've merged and updated the issues.
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>