Thanks Chaitanya
** Description changed:
+ [Impact]
+ When under memory pressure, tcmalloc will consume increasing amounts of CPU
cycles resulting in performance degradation; the mechanism to permit a larger
thread cache is broken, so the pinch point can be worked around by increasing
the
I've shoved the proposed patched version of gperftools into:
https://launchpad.net/~james-page/+archive/ubuntu/ceph-sru
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to google-perftools in Ubuntu.
Please find source of the test program to verify this bug at
http://pastebin.com/KAxQZARm
compile it with -ltcmalloc
To test:
Export a non-default value of the cache size, for eg # export
TCMALLOC_MAX_TOTAL_THREAD_CACHE_BYTES=67108864
Run the test prog, For the buggy version you will see
vivid has 2.2.1 - marking Fix Released.
** Changed in: google-perftools (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: google-perftools (Ubuntu Trusty)
Status: New = Triaged
** Changed in: google-perftools (Ubuntu Vivid)
Importance: Undecided = High
--
You received
** Branch linked: lp:~james-page/ubuntu/trusty/google-
perftools/bug-1439277
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to google-perftools in Ubuntu.
https://bugs.launchpad.net/bugs/1439277
Title:
tcmalloc performance degredation
From the upstream bug:
What steps will reproduce the problem?
1. export TCMALLOC_MAX_TOTAL_THREAD_CACHE_BYTES=10
2. run program A with -ltcmalloc
3. check memory used by program A
ps: A is a multithread program(with 80+ threads) which alloc/free memory
repeatedly
What is the expected