Re: [Proposal] Use jemalloc as default memory allocator for Mesos

build process for jemalloc > against a specific branch. We already maintain local changes for some other > 3rd party dependencies. > > /Jeff > > -Original Message- > From: Benno Evers [mailto:bev...@mesosphere.com] > Sent: Tuesday, September 5, 2017 4:02 AM > To: dev@

RE: [Proposal] Use jemalloc as default memory allocator for Mesos

Evers [mailto:bev...@mesosphere.com] Sent: Tuesday, September 5, 2017 4:02 AM To: dev@mesos.apache.org Subject: Re: [Proposal] Use jemalloc as default memory allocator for Mesos Hi Jeff, do you have a particular alternative in mind? Certainly SmartHeap is a non-starter because it is proprietary. I

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

gt; What's the availability of both jemalloc and tcmalloc on the Windows > >> platform? Do the products work there properly? > >> > >> There are solutions that I know work on Windows (from past work I've > >> done). I'm unsure about either jemalloc and tcmalloc, h

RE: [Proposal] Use jemalloc as default memory allocator for Mesos

ubject: Re: [Proposal] Use jemalloc as default memory allocator for Mesos I looked at the Windows build a bit closer, and the Cygwin requirement appears to simply be for the use of autogen to generate headers. Once the headers are generated, the rest of the build is driven by a committed Visual

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

er jemalloc and tcmalloc, however. Thanks, /Jeff -Original Message- From: Benno Evers [mailto:bev...@mesosphere.com] Sent: Tuesday, August 22, 2017 3:16 AM To: dev@mesos.apache.org Subject: Re: [Proposal] Use jemalloc as default memory allocator for Mesos Hi Alexander, in general, jemalloc and

RE: [Proposal] Use jemalloc as default memory allocator for Mesos

...@me.com] Sent: Wednesday, August 30, 2017 6:27 PM To: dev@mesos.apache.org Subject: Re: [Proposal] Use jemalloc as default memory allocator for Mesos It appears that jemalloc does support Windows (64bit) See: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjemalloc

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

erly? >> >> There are solutions that I know work on Windows (from past work I've >> done). I'm unsure about either jemalloc and tcmalloc, however. >> >> Thanks, >> >> /Jeff >> >> -Original Message----- >> From: Benno Evers [mailt

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

her jemalloc and tcmalloc, however. >> >> Thanks, >> >> /Jeff >> >> -Original Message----- >> From: Benno Evers [mailto:bev...@mesosphere.com] >> Sent: Tuesday, August 22, 2017 3:16 AM >> To: dev@mesos.apache.org >> Subject: Re:

RE: [Proposal] Use jemalloc as default memory allocator for Mesos

day, August 25, 2017 6:28 AM To: dev@mesos.apache.org Subject: Re: [Proposal] Use jemalloc as default memory allocator for Mesos Hi Jeff, from looking around on the internet, it seems like Firefox builds with jemalloc on all platforms, and I've also seen reports of people successfully using tcm

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

Windows (from past work I've > done). I'm unsure about either jemalloc and tcmalloc, however. > > Thanks, > > /Jeff > > -Original Message- > From: Benno Evers [mailto:bev...@mesosphere.com] > Sent: Tuesday, August 22, 2017 3:16 AM > To: dev@mesos.apache.org &g

RE: [Proposal] Use jemalloc as default memory allocator for Mesos

Message- From: Benno Evers [mailto:bev...@mesosphere.com] Sent: Tuesday, August 22, 2017 3:16 AM To: dev@mesos.apache.org Subject: Re: [Proposal] Use jemalloc as default memory allocator for Mesos Hi Alexander, in general, jemalloc and tcmalloc are very similar, and seem to be taking ideas from

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

Hi Alexander, in general, jemalloc and tcmalloc are very similar, and seem to be taking ideas from each other (in fact the jeprof executable started as a copy of pprof and there are still references the pprof documentation in some comments) >From what I've seen, the main difference is that the

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

Hi Benno, This does sound like a great addition to Mesos. Can you however explain how jemalloc is better than tcmalloc? I think that for such important change, we probably need some more information. Your comment in MESOS-7876 mentions that we already have tcmalloc since it is part of

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

I'm for making jemalloc default as well with adding an opt-out option to CMake and autotools build scripts. On Sat, Aug 19, 2017 at 3:23 AM, Benjamin Mahler wrote: > This will be a big win Benno, thanks for driving it! > > Nice to see that the heap profiling overhead is

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

This will be a big win Benno, thanks for driving it! Nice to see that the heap profiling overhead is really low, I'd love to be able to just hit an endpoint on the master or agent and get a memory profile. I'm a +1 for making it the default, however, I seem to recall hearing that there were some

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

Strongly in favor of this idea and willing to try it once it's available. On Fri, Aug 18, 2017 at 8:37 AM, James Peach wrote: > > > On Aug 18, 2017, at 3:49 AM, Benno Evers wrote: > > > > Hi all, > > > > I would like to propose bundling jemalloc as a

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

> On Aug 18, 2017, at 3:49 AM, Benno Evers wrote: > > Hi all, > > I would like to propose bundling jemalloc as a new dependency > under `3rdparty/`, and to link Mesos against this new memory > allocator by default. I support doing this for all the Mesos executable

[Proposal] Use jemalloc as default memory allocator for Mesos

Hi all, I would like to propose bundling jemalloc as a new dependency under `3rdparty/`, and to link Mesos against this new memory allocator by default. # Motivation The Mesos master and agent binaries are, ideally, very long-running processes. This makes them susceptible to memory issues,