simpler design and more performant (in both memory and CPU, which is a nice
surprise, actually), but there's a really slow memory leak. Maybe 10-20
megs per hour, according to the garbage collector. Not terrible, but any
kind of leak just drives me nuts. I just started dumping heap stats every
hour, and I get something like this:
Total: 233.1 MB
89.1 38.2% 38.2% 89.1 38.2% cnew
77.0 33.0% 71.2% 77.0 33.0% compress/flate.NewReader
10.8 4.6% 75.9% 12.2 5.3% net/http.(*Transport).getIdleConnCh
9.5 4.1% 79.9% 13.5 5.8% importer/twitter.func·005
9.0 3.9% 83.8% 63.0 27.0% net/http.(*Transport).dialConn
Over time that top line starts getting larger and larger while the ones
below stay about the same. So I think that's where the issue is, and yet
that line is the least helpful line possible. From what I can tell it comes
from this in malloc.goc:
runtime·mallocgc(typ->size*n, flag, 1, 1);
So... I've gone a long way to find out that my leak is caused by memory
being allocated. I'm at a bit of a dead end here. Any help would be greatly
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.