Try this HBase YCSB client instead:
https://github.com/apurtell/ycsb/tree/new_hbase_client
The HBase YCSB driver in the master repo holds on to one HTable instance
per driver thread. We accumulate writes into a 12MB write buffer before
flushing them en masse. This is why the behavior you are
Thank you Andrew, this is an excellent answer, I get it now. I will try your
hbase client for a 'fair' test :-)
Best Regards,
Ming
-Original Message-
From: Andrew Purtell [mailto:apurt...@apache.org]
Sent: Thursday, November 13, 2014 2:08 AM
To: user@hbase.apache.org
Cc: DeRoo, John
Thanks Andrew. This would be a very useful information along with the
github link.
Regards
Ram
On Thu, Nov 13, 2014 at 9:00 AM, Liu, Ming (HPIT-GADSC) ming.l...@hp.com
wrote:
Thank you Andrew, this is an excellent answer, I get it now. I will try
your hbase client for a 'fair' test :-)
Hi, all,
I am trying to use YCSB to test on our HBase 0.98.5 instance and got a strange
result: update is 6x better than read. It is just an exercise, so the HBase is
running in a workstation in standalone mode.
I modified the workloada shipped with YCSB into two new workloads: workloadr
and