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

Posted to issues@kudu.apache.org by "David Alves (JIRA)" <ji...@apache.org> on 2016/09/16 06:43:20 UTC

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

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

David Alves commented on KUDU-1622:
-----------------------------------

You mean ResultTracker, right? I have a few ideas and can take this on.

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