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.
go version devel +c7754c8 Tue Jan 19 06:20:36 2016 +0000 linux/amd64
SVG profile for my program shows:
You can see that as if reflect.Value.call directly allocates a lot. This does not make sense.
In text profile I see records that are probably these reflect.Value.call allocations. But in SVG they are trimmed at reflect.Value.call. RPC servers can allocate most of its memory during request serving, so this is pretty unfortunate.
go version devel +c7754c8 Tue Jan 19 06:20:36 2016 +0000 linux/amd64
SVG profile for my program shows:
You can see that as if reflect.Value.call directly allocates a lot. This does not make sense.
In text profile I see records that are probably these reflect.Value.call allocations. But in SVG they are trimmed at reflect.Value.call. RPC servers can allocate most of its memory during request serving, so this is pretty unfortunate.
The text was updated successfully, but these errors were encountered: