FAQ
Hi All

Just to conclude this thread.

I managed to find the issue and, as expected, it was in my code :)

I had been appending to a slice which the intention of cleaning it up when
a certain error occurred However, that error never actually occurred in
production and so the slice kept growing.

Thanks for your help

Ryan
On Sunday, 20 January 2013 20:23:36 UTC, Rémy Oudompheng wrote:
On 2013/1/20 Rémy Oudompheng <remyoud...@gmail.com <javascript:>> wrote:
On 2013/1/20 Dave Cheney <da...@cheney.net <javascript:>> wrote:
Hi Remy, do you think this is a problem than should be addressed? Ie,
should all the flags that control recording of profiling allocation default
to a value that will not allocate unless profiling is requested?
It's a problem in Go 1 because profiling data is unnecessarily big
(can take hundreds of MB when the arena becomes a few GB large).

But in Go 1.1 it will be better because of
http://code.google.com/p/go/source/detail?r=ef500247af6f

The occupied size will have a similar order of magnitude as the map in
runtime.mheap.

Rémy.
So I don't think we need to do anything. If you need more than 50MB of
memory for profiling data, with default settings, your program is
already using so much memory it cannot be your main issue.

Rémy.
--

Search Discussions

Discussion Posts

Previous

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 14 of 14 | next ›
Discussion Overview
groupgolang-nuts @
categoriesgo
postedJan 20, '13 at 3:11p
activeJan 25, '13 at 9:37a
posts14
users5
websitegolang.org

People

Translate

site design / logo © 2021 Grokbase