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-1938) Make in-memory table scanning faster
Date Wed, 27 Jul 2011 02:15:10 GMT

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

stack updated HBASE-1938:
-------------------------

    Fix Version/s: 0.92.0
         Assignee: nkeywal  (was: stack)
     Hadoop Flags: [Reviewed]
           Status: Patch Available  (was: Open)

Assigning nkeywal. Marking patch available against 0.92.

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

        

Mime
View raw message