Closed
Bug 1442705
Opened 7 years ago
Closed 6 years ago
Further test autopush malloc options
Categories
(Cloud Services Graveyard :: Operations: Autopush, task)
Cloud Services Graveyard
Operations: Autopush
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pjenvey, Assigned: oremj)
Details
Our test run of a few autopush nodes on prod w/ the env var MALLOC_ARENA_MAX=2 showed less memory usage overall (albeit w/ the same rate of increase as without it).
So let's default stage/prod to a safe default of MALLOC_ARENA_MAX=2 on our next deploy.
Meanwhile, a new test on prod of MALLOC_ARENA_MAX=1 would be useful to compare it to. And even more importantly a comparison of these tuned glibc mallocs to jemalloc.
So on top of the MALLOC_ARENA_MAX=2 default, let's also deploy both a couple endpoint/connection nodes with a MALLOC_ARENA_MAX=1 and separately USE_JEMALLOC=true, to compare all 3 settings.
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → oremj
Assignee | ||
Comment 1•7 years ago
|
||
MALLOC_ARENA_MAX=2 is on by default as of 1.41.0
Reporter | ||
Comment 2•7 years ago
|
||
Thanks Jeremy. If you have a chance tomorrow can we deploy 1.42.0 w/ the other 2 settings on a couple nodes?
Assignee | ||
Comment 3•6 years ago
|
||
I think we did this, but please reopen/ping if anything else is needed here.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•