mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Peach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7876) Investigate alternative malloc implementations for mesos
Date Tue, 15 Aug 2017 18:21:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127667#comment-16127667
] 

James Peach commented on MESOS-7876:
------------------------------------

FWIW we run in production with jemalloc. I don't think you can switch Mesos entirely over
to always using jemalloc since we ship shared libraries that get used by apps that are not
prepared to have jemalloc thrust upon them.

> Investigate alternative malloc implementations for mesos
> --------------------------------------------------------
>
>                 Key: MESOS-7876
>                 URL: https://issues.apache.org/jira/browse/MESOS-7876
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Benno Evers
>            Assignee: Benno Evers
>         Attachments: jemalloc_benchmark_raw.txt, malloc.cpp, noprof.png, prof.png
>
>
> It is currently very hard to debug memory issues, in particular memory leaks, in mesos.
> An alluring way to improve the situation would be to change the default malloc to jemalloc,
which has built-in heap-tracking capabilities.
> However, some care needs to be taken when considering to change such a fundamental part
of mesos:
>   * Would such a switch have any adverse impact on performance?
>   * Is it available and will it compile on all our target platforms?
>   * Is the jemalloc-licensing compatible with bundling as third-party library?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message