Yes, this is the only stress test running on the cluster and nothing else. And it all goes to block cache as evidenced by metrics.
2011-04-20 12:28:48,375 DEBUG org.apache.hadoop.hbase.io.hfile.LruBlockCache: LRU Stats: total=8.26 MB, free=190.08 MB, max=198.34 MB, blocks=112, accesses=55732209, hits=55732083, hitRatio=99.99%%, cachingAccesses=55732195, cachingHits=55732083, cachingHitsRatio=99.99%%, evictions=0, evicted=0, evictedPerRun=NaN On Wed, Apr 20, 2011 at 12:25 PM, Stack <[email protected]> wrote: > On Wed, Apr 20, 2011 at 12:25 PM, Stack <[email protected]> wrote: >> On Tue, Apr 19, 2011 at 4:46 PM, Dmitriy Lyubimov <[email protected]> >> wrote: >>> Right now i am shooting scans returning between 3 and 40 rows and >>> regardless of data size, approximately 500-400 QPS. The data tables >>> are almost empty and in-memory, so they surely should fit in those 40% >>> heap dedicated to them. >>> >> >> How many clients are going against the cluster? If you use less, do >> your numbers improve? >> > > And all these clients are going against a single 40 row table? > St.Ack >
