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

Posted to issues@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2015/12/30 00:07:49 UTC

[jira] [Updated] (HBASE-15047) Try spin lock for MVCC completion

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

Elliott Clark updated HBASE-15047:
----------------------------------
    Attachment: HBASE-15047.patch

This will greatly change the way perf/flame graphs look. We will now be in user mode code a lot more.

However that should result in much faster response times as there should be no scheduler overhead.

> Try spin lock for MVCC completion
> ---------------------------------
>
>                 Key: HBASE-15047
>                 URL: https://issues.apache.org/jira/browse/HBASE-15047
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>         Attachments: HBASE-15047.patch
>
>
> Waits/Notify is very very expensive since it can cost a thread scheduling. There should only ever be a few threads ( < Num Cores ) running. So it should be possible to spin and use compare and swap to update the read point.



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