hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Asaf Mesika <asaf.mes...@gmail.com>
Subject Re: write throughput in cassandra, understanding hbase
Date Tue, 22 Jan 2013 20:57:05 GMT
Sent from my iPhone

On 22 בינו 2013, at 20:47, Jean-Daniel Cryans <jdcryans@apache.org> wrote:

On Tue, Jan 22, 2013 at 10:38 AM, S Ahmed <sahmed1020@gmail.com> wrote:

I've read articles online where I see cassandra doing like 20K writers per

second, and hbase around 2-3K.

Numbers with 0 context don't mean much, if at all.

I understand both systems have their strenghts, but I am curious as to what

is holding hbase from reaching similiar results?

Is it HDFS that is the issue?  Or hbase does certain things (to its

advantage) that slows the write path down?

Our writes are generally quite fast, I think at the moment some
improvements can be made at the client level. I did some tests last
year and I could get better throughput with the asynchbase client
compared to the normal Java client because the former has call queues
per region server. Both tests were using the same region servers,
uploading the same data set.

Can you elaborate more on why asynchronous hbase client is better?


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