hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4163) Create Split Strategy for YCSB Benchmark
Date Sat, 07 Dec 2013 09:41:48 GMT

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

Hudson commented on HBASE-4163:
-------------------------------

SUCCESS: Integrated in HBase-TRUNK #4715 (See [https://builds.apache.org/job/HBase-TRUNK/4715/])
Add note on how to presplit for ycsb from HBASE-4163 (stack: rev 1548760)
* /hbase/trunk/src/main/docbkx/book.xml


> Create Split Strategy for YCSB Benchmark
> ----------------------------------------
>
>                 Key: HBASE-4163
>                 URL: https://issues.apache.org/jira/browse/HBASE-4163
>             Project: HBase
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.90.3, 0.92.0
>            Reporter: Nicolas Spiegelberg
>            Assignee: Luke Lu
>            Priority: Minor
>              Labels: benchmark
>             Fix For: 0.99.0
>
>
> Talked with Lars about how we can make it easier for users to run the YCSB benchmarks
against HBase & get realistic results.  Currently, HBase is optimized for the random/uniform
read/write case, which is the YCSB load.  The initial reason why we perform bad when users
test against us is because they do not presplit regions & have the split ratio really
low.  We need a one-line way for a user to create a table that is pre-split to 200 regions
(or some decent number) by default & disable splitting.  Realistically, this is how a
uniform load cluster should scale, so it's not a hack.  This will also give us a good use
case to point to for how users should pre-split regions.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message