hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3707) Flush memstore after a configurable number of inserts not simply based on size
Date Tue, 29 Mar 2011 00:20:05 GMT

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

Andrew Purtell commented on HBASE-3707:
---------------------------------------

Running this under the profiler I find this change keeps the time for Store#upsert proportional
to that for HRegion#getLastIncrement, at about 30% each for an Increment only workload. Otherwise
the relative time for getLastIncrement creeps up to about 70%.

> Flush memstore after a configurable number of inserts not simply based on size
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-3707
>                 URL: https://issues.apache.org/jira/browse/HBASE-3707
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Priority: Minor
>         Attachments: HBASE-3707.patch
>
>
> Memstore upsert performance may be impacted by having a large number of values in the
map. Consider flushing the store after a configurable number of inserts.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message