Skip to content
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.

Test autopush/endpoint w/ low MALLOC_ARENA_MAX values and jemalloc #79

Closed
pjenvey opened this issue Dec 19, 2017 · 2 comments
Closed

Test autopush/endpoint w/ low MALLOC_ARENA_MAX values and jemalloc #79

pjenvey opened this issue Dec 19, 2017 · 2 comments
Assignees
Labels

Comments

@pjenvey
Copy link
Member

pjenvey commented Dec 19, 2017

We appear to be suffering from glibc malloc using excessive memory w/ our allocation patterns, similar to the situation described here:

http://codearcana.com/posts/2016/07/11/arena-leak-in-glibc.html

We need to see what memory improvements can be seen w/ autopush/endpoint under a MALLOC_ARENA_MAX=1

We currently have a couple nodes running at a more conservative MALLOC_ARENA_MAX=2. We're still seeing the same rate of growth, however the total RSS used has been cut by about 33% under endpoint, and about 20% under autopush.

@pjenvey pjenvey self-assigned this Dec 19, 2017
@pjenvey pjenvey added the ready label Jan 17, 2018
@pjenvey pjenvey changed the title Test autopush/endpoint w/ low MALLOC_ARENA_MAX values Test autopush/endpoint w/ low MALLOC_ARENA_MAX values and jemalloc Mar 5, 2018
@pjenvey
Copy link
Member Author

pjenvey commented Mar 5, 2018

Also jemalloc may show more improvement over glibc malloc, support for enabling it was added in mozilla-services/autopush#1100

@bbangert
Copy link
Member

Memory use is pretty solid now and the crypto is faster. Remaining work is obsolete per Rust move this year.

@bbangert bbangert removed the ready label Jan 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants