One thing you might want to look at is HTableUtil. It's on trunk, but you can look at the source and port it to whatever version you are using.
We've found that region-sorting helps a lot by minimizing the number of RS calls in any given flush. On 8/11/11 5:57 PM, "Jean-Daniel Cryans" <[email protected]> wrote: >I'm sure you've already seen this but just to be sure, do read >http://hbase.apache.org/book/perf.writing.html > >Auto-flush is always on unless you turn it off yourself. Using >HTable.batch still respects this except that it flushes all the rows >at the same time. > >If you have fat values to insert and you can compress them, I would >recommend doing so client-side. > >J-D > >On Wed, Aug 10, 2011 at 11:35 PM, Steinmaurer Thomas ><[email protected]> wrote: >> Hello, >> >> >> >> our test data generator client uses HTable.batch to transfer puts to the >> server. For example, I think auto flush at table-level is off when >> running batches? Any other client API side optimizations when working >> with HTable.batch? We have writing to the WAL disabled already. >> >> >> >> Thanks, >> >> Thomas >> >> >> >>
