hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 史英杰 <shiyingjie1...@gmail.com>
Subject Why data read performs better than data write in HBase?
Date Wed, 23 Jun 2010 12:32:10 GMT
Hi, All
    Recently I did some tests on HBase, using the performance eveluation
package  in HBase 0.20.3. There are some situations I can't understand. I
found that read perform better than write, no matter sequential read or
random read during the test. But in BigTable's paper, writes perform better
than reads, because each tablet server appends all incoming writes to a
single commit log and uses group commit to stream these writes efficiently
to GFS. In HBase, we set the autoFlush=false, and the flush size is 64M, so
writes should perform better than reads, but the result is just the
opposite. Please help me to explain this phenomenon, thanks a lot!


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message