[
https://issues.apache.org/jira/browse/KUDU-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367912#comment-16367912
]
Todd Lipcon commented on KUDU-636:
----------------------------------
Brain dump update on some of the points above:
1) Threadpool is now LIFO as of 1.7 which should help keep a smaller number of
threads with "hot" caches
2) We've removed almost all of the per-tablet threads and they now use shared
threadpools
3) we should still look into thread cache tuning. perhaps we could even have
kudu automatically tune at runtime to allow large thread caches when the
process memory is under its soft threshold and then tune it down as it reaches
its high threshold. Then we wouldn't need users to concern themselves with this
tuning parameter.
4) we're on PB3 now but haven't yet switched on arena support
> optimization: we spend a lot of time in alloc/free
> --------------------------------------------------
>
> Key: KUDU-636
> URL: https://issues.apache.org/jira/browse/KUDU-636
> Project: Kudu
> Issue Type: Improvement
> Components: perf
> Affects Versions: Public beta
> Reporter: Todd Lipcon
> Priority: Major
>
> Looking at a workload in the cluster, several of the top 10 lines of perf
> report are tcmalloc-related. It seems like we don't do a good job of making
> use of the per-thread free-lists, and we end up in a lot of contention on the
> central free list. There are a few low-hanging fruit things we could do to
> improve this for a likely perf boost.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
