You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/12/07 00:53:36 UTC

[jira] [Resolved] (HBASE-4163) Create Split Strategy for YCSB Benchmark

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

stack resolved HBASE-4163.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.99.0
         Assignee: Luke Lu  (was: Lars George)

Closing as fixed.  I also added note to our little ycsb section in the doc that will show the next time I push the site; it points at Luke's little script.

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