You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/04/11 23:06:13 UTC

[jira] Commented: (HBASE-61) [hbase] Create an HBase-specific MapFile implementation

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

Jim Kellerman commented on HBASE-61:
------------------------------------

I ran some performance tests today and the results were not pretty.

Doing 1,048,576 sequential writes through HBase onto the local file system achieved 3,620 writes per second.

Writing 1,048,576 records sequentially into a MapFile onto the local file system was slightly better at 5,674 writes per second.


> [hbase] Create an HBase-specific MapFile implementation
> -------------------------------------------------------
>
>                 Key: HBASE-61
>                 URL: https://issues.apache.org/jira/browse/HBASE-61
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: io
>            Reporter: Bryan Duxbury
>            Priority: Minor
>
> Today, HBase uses the Hadoop MapFile class to store data persistently to disk. This is convenient, as it's already done (and maintained by other people :). However, it's beginning to look like there might be possible performance benefits to be had from doing an HBase-specific implementation of MapFile that incorporated some precise features.
> This issue should serve as a place to track discussion about what features might be included in such an implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.