accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4458) lock contention around configuration settings impacts tablet server performance
Date Thu, 15 Sep 2016 19:29:22 GMT

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

Christopher Tubbs commented on ACCUMULO-4458:
---------------------------------------------

Also, containsKey(key) followed by get(key) is unnecessarily inefficient. Just do a get, and
check if it's null.

Also, since this was committed already to 1.8, I'm going to merge it to master... because
I'm merging another change, and this one hasn't yet been merged to master, so it'll get picked
up with mine.

> lock contention around configuration settings impacts tablet server performance
> -------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4458
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4458
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.7.1, 1.8.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>         Attachments: ACCUMULO-4458-1.7.v1.patch
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> While investigating a pretty severe performance regression comparing YCSB against 1.6
and 1.7, I found a fair bit of lock contention around getting configuration values. This was
improved by ACCUMULO-4388, but various threads eventually all started contending on the configuration
values expected from the site xml files.



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

Mime
View raw message