Open GoogleCodeExporter opened 9 years ago
the code to see the issue
Original comment by sirwmsha...@gmail.com
on 19 Mar 2015 at 7:55
Attachments:
tcmalloc documentation is actually somewhat stale. Since before 2.0 (I don't
recall exact version) it is using SLAB-ful memory management for blocks up to
256k.
That virtual address space size grows slowly is likely some virtual address
space fragmentation. If you don't see RSS growing, then it is harmless.
Running your program for a bit I don't see RSS growth. And I did see some VSS
growth but it stopped occurring.
It looks like most of VSS is actually thread stacks, that's why it looks
somewhat scary.
Original comment by alkondratenko
on 22 Mar 2015 at 8:20
thanks ...
my own tests match agree with your statements.
but...
I am going to have customers that will monitor memory usage
of the deployed program. Seeing a 'step-function' for memory ( attachment )
is going to create a headache for my support team as they will have to explain
this.
can you point me to a code source file that confirms that 64k buffers are
managed similar to 1k buffers ?
Original comment by sirwmsha...@gmail.com
on 24 Mar 2015 at 1:02
Attachments:
Original issue reported on code.google.com by
sirwmsha...@gmail.com
on 19 Mar 2015 at 7:49