You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2017/09/06 00:08:01 UTC
[jira] [Updated] (MESOS-7876) Investigate alternative malloc
implementations for mesos
[ https://issues.apache.org/jira/browse/MESOS-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-7876:
------------------------------
Sprint: Mesosphere Sprint 62, Mesosphere Sprint 63 (was: Mesosphere Sprint 62)
> 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
> Labels: mesosphere, performance
> 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)