hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6755) HRegion.internalObtainRowLock uses unecessary AtomicInteger
Date Sat, 22 Sep 2012 22:00:08 GMT

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

stack updated HBASE-6755:
-------------------------

    Priority: Minor  (was: Major)
    
> HRegion.internalObtainRowLock uses unecessary AtomicInteger
> -----------------------------------------------------------
>
>                 Key: HBASE-6755
>                 URL: https://issues.apache.org/jira/browse/HBASE-6755
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Minor
>             Fix For: 0.94.3, 0.96.0
>
>         Attachments: 6755-0.96.txt
>
>
> I was looking at HBase's implementation of locks and saw that is unnecessarily uses an
AtomicInteger to obtain a unique lockid.
> The observation is that we only need a unique one and don't care if we happen to skip
one.
> In a very unscientific test I saw the %system CPU reduced when the AtomicInteger is avoided.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message