You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/03/07 20:46:40 UTC

[jira] [Updated] (KUDU-1366) Consider switching to jemalloc

     [ https://issues.apache.org/jira/browse/KUDU-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated KUDU-1366:
------------------------------
    Attachment: Kudu Benchmarks.pdf

attached benchmark report of tcmalloc vs jemalloc. A few big wins, a few big losses (particularly wire_protocol-test got twice as slow). Worth looking into what happened there, since it probably is a big factor in why some of the macro benchmarks got slower.

> Consider switching to jemalloc
> ------------------------------
>
>                 Key: KUDU-1366
>                 URL: https://issues.apache.org/jira/browse/KUDU-1366
>             Project: Kudu
>          Issue Type: Bug
>          Components: build
>            Reporter: Todd Lipcon
>         Attachments: Kudu Benchmarks.pdf
>
>
> We spend a fair amount of time in the allocator. While we could spend some time trying to use arenas more, it's also worth considering switching allocators. I ran a few quick tests with jemalloc 4.1 and it seems like it might be better than the version of tcmalloc that we use (and has much more active development)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)