Sorry, Its been one of those days.
---------------------------------------- > From: [email protected] > To: [email protected] > Subject: RE: HBase Transaction per second in Map-Reduce > Date: Tue, 24 May 2011 14:18:28 -0500 > > > > Himanish, > > Are we talking about an African or European Swallow? > (Sorry its a reference to the Monty Python movie scene where they cross the > bridge after being asked 3 questions which they must answer correctly? > [What's the forward air speed velocity of an unladen swallow?]) > > The point is that you're asking a question which has no valid answer because > there are so many variables that will effect the timings. > > Just to list a couple of the things that will impact your performance: > 1) Hardware > 2) Network topology > 3) Table schema. > 4) Tuning of Hadoop environment > 5) Caching? Oh wait, that could be considered Tuning. > > So while I can understand that you want to improve your performance, you > really have to get down and look at a couple of larger issues. > > -Mike > > PS. Whatever expectations you have, you'll need to lower them. ;-) > > ---------------------------------------- > > Date: Tue, 24 May 2011 14:31:21 -0400 > > Subject: HBase Transaction per second in Map-Reduce > > From: [email protected] > > To: [email protected] > > > > Hi, > > > > Could anybody please point to some article or paper which can give an > > understanding of the transaction per second (both read and write) that is > > supported or seen to be accomplished using HBase Map-Reduce. > > > > We have written few HBase Map-reduces which are not giving us the > > desired/expected performance . > > > > -- > > Thanks & Regards > > Himanish >
