Bug 1301229 - [doc] TCmalloc 2.4 tunable thread cache size
Summary: [doc] TCmalloc 2.4 tunable thread cache size
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Documentation
Version: 1.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 1.3.2
Assignee: Bara Ancincova
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-22 22:35 UTC by Federico Lucifredi
Modified: 2016-03-01 08:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-01 08:23:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1297502 0 unspecified CLOSED [RFE] Add support for modifying the TCMalloc thread cache 2022-02-21 18:18:20 UTC

Internal Links: 1297502

Description Federico Lucifredi 2016-01-22 22:35:53 UTC 
Description of problem:


RHCS 1.3.2 runs on RHEL 7.2's TCmalloc (version 2.4) which allows tuning of the thread cache.

We need to document 

1. What the default is (128MB)
2. That it changed from previous releases, where it was 32MB
3. How to change the thread cache size from ceph.conf. Sage wrote a patch to take care of this, bug 1297502 tracks that RFE.
Comment 2 Federico Lucifredi 2016-01-22 22:38:16 UTC 
This is one of two late-breaking doc bugs. Anjana has been informed.
Comment 3 Ken Dreyer (Red Hat) 2016-02-03 16:45:27 UTC 
Please note that the config file to change is:

/etc/sysconfig/ceph (RHEL)

/etc/default/ceph (Ubuntu)
Comment 7 rakesh 2016-02-05 19:28:30 UTC 
This bug is not seen in ubuntu. I have checked in "/etc/default/ceph" of Jan 26th 2016 build and the value is TCMALLOC_MAX_TOTAL_THREAD_CACHE_BYTES=128MB in all the osds. However the bug has been verified by Rachana in RHEL. So moving it to Verified stage.
Note You need to log in before you can comment on or make changes to this bug.