Noticed discussion on this thread. We filed HBASE-2939 with patch
On Thu, Sep 9, 2010 at 11:10 PM, tsuna <[email protected]> wrote: > On Thu, Sep 9, 2010 at 1:48 PM, MauMau <[email protected]> wrote: > > From: "tsuna" <[email protected]> > >> In my recent loadtests on my HBase-heavy application (be it with > >> HBase's traditional client or with asynchbase) I've always been CPU > >> bound (except sometimes HBase's traditional client incurs too much > >> lock contention to really max out the CPU cores, but this is entirely > >> unrelated to the code you're quoting above). > > > > Thank you for sharing your precious experience and knowledge. I > understood. > > I'm relieved to know that many threads in one HBase client process can > max > > out CPUs in most cases. I'm sorry to have interrupted discussion. > > Note that HBase clients aren't always CPU-bound, but all my recent > loadtests for my application are. Some clients can be network-bound, > but for those clients adding more connections won't buy you anything > if the NIC is already maxed out. Your mileage will vary wildly > depending on how you use HBase. > > -- > Benoit "tsuna" Sigoure > Software Engineer @ www.StumbleUpon.com >
