[jira] [Commented] (KUDU-1622) ResultTracker exhibits high contention under non-batched write workload

["Todd Lipcon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15724039#comment-15724039 ] 

Todd Lipcon commented on KUDU-1622:
-----------------------------------

e98e4b6d826c8a76d532e85e254981ba5298e991 should improve this a bit. Let's re-evaluate and if it's still high contention we can try striping the tracker (prototyped here: https://gerrit.cloudera.org/#/c/5322/ )

> ResultTracker exhibits high contention under non-batched write workload
> -----------------------------------------------------------------------
>
>                 Key: KUDU-1622
>                 URL: https://issues.apache.org/jira/browse/KUDU-1622
>             Project: Kudu
>          Issue Type: Improvement
>          Components: perf, rpc
>    Affects Versions: 1.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: fg.svg, pprof13384.0.svg
>
>
> I am running a YCSB workload with non-batched writes, and I see ResultCache among the highest CPU consumers (>15% of the CPU). There's a lot of lock contention on the result cache map. We should consider a more concurrent data structure and/or finer-grained locking.



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