Comment #4 on issue 96 by tru64ufs: prefix structure memory leak
http://code.google.com/p/memcached/issues/detail?id=96
Yes, Trond, I agree that it is not a memory leak. I just wanted to get your
attention ;-)
But the thing is that on a real production server, constant RSS in process
memory with no clue can be a real
pain and can lead to real performance problem in the end since it will
start swapping due to physical memory
requirement. And also it is not easy for us to simply issue "stats reset"
command since we are keep track of
these statistics in RRD file and if you reset them, the RRD file and chart
will be all messed up.
Furthermore, we ran into problems when people forgot to put their prefix in
the app; our memcached stats
collection server hung with using up 100% CPU cycle collecting all that
unique keys as prefix statistics.
Trond. I think ignoring keys with no prefix in the prefix stat is perfectly
fine for us.
Thank you for your reply.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
