The current plan is to polish and publish our learnings by the end of next
month (June 2018).
On Sunday, May 13, 2018 at 11:48:45 PM UTC-4, Ian Lance Taylor wrote:
>
> [ +rlh, austin]
>
> On Sun, May 13, 2018 at 11:24 AM, Tanya Borisova > wrote:
> > Hi!
> >
> > Is Golang team still working
Hard telling what it going on. 35MB, even for 1 CPU, seems very small. Most
modern system provision more than 1GB per HW thread though I've seen some
provision as little as 512MB. GOGC (SetGCPercent) can be adjust so that the
application uses more of the available RAM. Running with GODEBUG=gctra
Without building and measuring it is impossible to know which of these
approaches, or even a third one where you simply run a single instance, is
best for your application.
Each approach has upsides and downsides. The GC believes GOMAXPROCS and
will uses as much CPU as it believes is available.
Nothing is obvious but there is something going on we don't understand. If
you have the time to create a simple reproducer the next step would be to
open an issue that contains the reproducer. Once the problem can be
reproduced locally it can be diagnosed.
On Wednesday, June 7, 2017 at 11:37:2
The Johnstone / Wilson paper "The memory fragmentation problem: solved?"
[1] is the original source.
Modern malloc systems including Google's TCMalloc, Hoard [2], and Intel's
Scalable Malloc (aka Mcrt Malloc [3]) all owe much to that paper and along
with other memory managers all segregate obje
