Thank you for your explanation. I was able to track this problem down to logic in one of the handlers periodically invoked by the page; the handler logic would result in the allocation pattern you described.
Best, -- Jiří Šimša On Tue, Oct 18, 2016 at 6:13 AM, <r...@golang.org> wrote: > From the trace (4->4->0) it looks like the app is allocating about 4MB > every 10ms. The app also has little (0 rounded) reachable data, sometimes > called heap ballast. Since there is little ballast the GC is attempting to > keep the heap from growing beyond 5MB. The GC is using about 2% of the CPU > resources to do its job. > > All of this seems perfectly reasonable from the GC's perspective. > > > On Tuesday, October 18, 2016 at 12:32:47 AM UTC-4, Jiří Šimša wrote: >> >> go version go1.7.1 darwin/amd64 >> >> -- >> Jiří Šimša >> >> On Mon, Oct 17, 2016 at 8:02 PM, Ian Lance Taylor <ia...@golang.org> >> wrote: >> >>> On Mon, Oct 17, 2016 at 6:20 PM, <jiri....@gmail.com> wrote: >>> > >>> > The backend of my web server (written in Go) have recently started >>> consuming >>> > large amounts of CPU. AFAICT, the CPU seems to be consumed by the >>> garbage >>> > collector and I would appreciate any information that would help me >>> track >>> > down the root cause. >>> >>> What version of Go? What platform? >>> >>> Ian >>> >> >> -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
