Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of eczech52@gmail.com designates
 209.85.217.169 as permitted sender)
MIME-Version: 1.0
Sender: eczech52@gmail.com
From: Eric Czech <eric@nextbigsound.com>
Date: Tue, 7 Aug 2012 09:35:16 -0400
Message-ID: 
 <CACjoVs+=Ocxxf5rtDUAeOU=TdW3b77uLyHLYtAjEiyGZHXUfLA@mail.gmail.com>
Subject: Ideal row size
To: user <user@hbase.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hello everyone,

I'm trying to store many small values in indexes created via MR jobs,
and I was hoping to get some advice on how to structure my rows.
Essentially, I have complete control over how large the rows should be
as the values are small, consistent in size, and can be grouped
together in any way I'd like.  My question then is, what's the ideal
size for a row in Hbase, in bytes?  I'm trying to determine how to
group my values together into larger values, and I think having a
target size to hit would make that a lot easier.

I know fewer rows is generally better to avoid the repetitive storage
of keys, cfs, and qualifiers provided that those rows still suit a
given application, but I'm not sure at what point the scale will tip
in the other direction and I'll start to see undue memory pressure or
compaction issues with rows that are too large.

Thanks in advance!