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

Todd Lipcon updated KUDU-1622:
------------------------------
    Summary: ResultTracker exhibits high contention under non-batched write 
workload  (was: ResultCache exhibits high contention under non-batched write 
workload)

> 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
>         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)

Reply via email to