hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "Hbase/PerformanceEvaluation" by stack
Date Fri, 25 Apr 2008 05:51:33 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by stack:
http://wiki.apache.org/hadoop/Hbase/PerformanceEvaluation

The comment on the change is:
Added 0.1.2 numbers

------------------------------------------------------------------------------
  
  Subsequently I profiled the mapfile PerformanceEvaluation.  Turns out generation of the
values and keys to insert were taking a bunch of CPU time. After making a fix key and value
generations were between 15-25% (the alternative was precompiling keys and values which would
take loads of memory).  Rerunning tests, it looks like there can be a pretty broad range of
fluctuation in mapfile numbers between runs.  I also noticed that the 0.15.x random reads
seem to be 50% faster than TRUNK.  Investigate.
  
+ == HBase 0.1.2 (Candidate) 04/25/2008 ==
+ 
+ Numbers for the 0.1.2 candidate.  The 'mapfile', '20071219', and '!BigTable' columns are
copied from the 'TRUNK 12/19/2007' above.  The new columns are for 0.1.2 and for mapfile in
0.16.3 hadoop (This latter test uses new MapFilePerformanceTest script).
+ 
+ ||<rowbgcolor="#ececec">Experiment Run||20071219||0.1.2||mapfile||mapfile0.16.3||!BigTable||
+ ||random reads ||167||351||685||644||1212||
+ ||random reads (mem)||Not implemented||Not implemented||Not Implemented||-||10811||
+ ||random writes||1400||2330||-||-||8850||
+ ||sequential reads||138||349||-||-||4425||
+ ||sequential writes||1691||2479||5494||6204||8547||
+ ||scans||3731||6278||25641||47662||15385||
+ 
+ We've near doubled in most areas over the hbase from 20071219.  Its a combination of improvements
in hadoop -- particularly scanning -- and in HBase itself (locking was redone, we customized
RPC to use codes rather than class names, etc.).
+ 

Mime
View raw message