Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 28 Jul 2011 15:40:10 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1431827759.15870.1311867610306.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-1938) Make in-memory table scanning
 faster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-1938:
------------------------------

Sounds great nkeywal.  Thanks for digging in here.

> Make in-memory table scanning faster
> ------------------------------------
>
>                 Key: HBASE-1938
>                 URL: https://issues.apache.org/jira/browse/HBASE-1938
>             Project: HBase
>          Issue Type: Improvement
>          Components: performance
>            Reporter: stack
>            Assignee: nkeywal
>            Priority: Blocker
>             Fix For: 0.90.4, 0.92.0
>
>         Attachments: 20110726_1938_KeyValueSkipListSet.patch, 20110726_1938_MemStore.patch, 20110726_1938_MemStoreScanPerformance.java, MemStoreScanPerformance.java, MemStoreScanPerformance.java, caching-keylength-in-kv.patch, test.patch
>
>
> This issue is about profiling hbase to see if I can make hbase scans run faster when all is up in memory.  Talking to some users, they are seeing about 1/4 million rows a second.  It should be able to go faster than this (Scanning an array of objects, they can do about 4-5x this).

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