[
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
new graphs with MALLOC_CONF=purge:decay (suggested by Jason Evans).
Substantially better. Spent some time looking at the wire_protocol-test
"regression" and eventually determined it's not malloc-related, but in fact
code-alignment related. Changing the allocator realigns some hot loops away
from 16-byte boundaries, which changes the perf significantly. Other metrics
look mostly positive (some very positive).
> 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, 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)
