2 ms·
> mandatory GC managed memory It can be a right old bugger - I've been tweaking gron's memory usage down as a side project (e.g. 1M lines of my sample file int
by zimpenfish 5y ago
> mandatory GC managed memory
It can be a right old bugger - I've been tweaking gron's memory usage down as a side project (e.g. 1M lines of my sample file into original gron uses 6G maxrss/33G peak, new tweaked uses 83M maxrss/80M peak) and there's a couple of pathological cases where the code seems to spend more time GCing than parsing, even with `runtime.GC()` forced every N lines. In C, I'd know where my memory was and what it was doing but even with things like pprof, I'm mostly in the dark with Go.