In our original test, we mistakenly ran the HBase test with
the hbase.hregion.memstore.mslab.enabled property set to false.  We re-ran
the test with the hbase.hregion.memstore.mslab.enabled property set to true
and have reported the results in the following addendum:

Addendum to Hypertable vs. HBase Performance
Test<http://www.hypertable.com/why_hypertable/hypertable_vs_hbase_2/addendum/>

Synopsis: It slowed performance on the 10KB and 1KB tests and failed the
100 byte and 10 byte tests with *Concurrent mode failure*

- Doug

-- 
You received this message because you are subscribed to the Google Groups 
"Hypertable Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/hypertable-dev?hl=en.

Reply via email to