[jira] [Closed] (HBASE-6284) Introduce HRegion#doMiniBatchMutation()

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

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

Lars Hofhansl closed HBASE-6284.
--------------------------------

    
> Introduce HRegion#doMiniBatchMutation()
> ---------------------------------------
>
>                 Key: HBASE-6284
>                 URL: https://issues.apache.org/jira/browse/HBASE-6284
>             Project: HBase
>          Issue Type: Bug
>          Components: Performance, regionserver
>            Reporter: Ted Yu
>            Assignee: Anoop Sam John
>             Fix For: 0.94.1, 0.96.0
>
>         Attachments: 6284_Trunk-Addendum.patch, 6284_Trunk-V3.patch, HBASE-6284_94.patch, HBASE-6284_Trunk.patch, HBASE-6284_Trunk-V2.patch, HBASE-6284_Trunk-V3.patch
>
>
> From Anoop under thread 'Can there be a doMiniBatchDelete in HRegion':
> The HTable#delete(List<Delete>) groups the Deletes for the same RS and make one n/w call only. But within the RS, there will be N number of delete calls on the region one by one. This will include N number of HLog write and sync. If this also can be grouped can we get better performance for the multi row delete.
> I have made the new miniBatchDelete () and made the HTable#delete(List<Delete>) to call this new batch delete.
> Just tested initially with the one node cluster.  In that itself I am getting a performance boost which is very much promising.
> Only one CF and qualifier.
> 10K total rows delete with a batch of 100 deletes. Only deletes happening on the table from one thread.
> With the new way the net time taken is reduced by more than 1/10
> Will test in a 4 node cluster also. I think it will worth doing this change.

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