10 tables are fine. 1000 are not, especially when one does table pre-splitting to increase write perf.
Too many regions kill HBase. Best regards, Vladimir Rodionov Principal Platform Engineer Carrier IQ, www.carrieriq.com e-mail: [email protected] ________________________________________ From: Jacques [[email protected]] Sent: Wednesday, February 15, 2012 3:45 PM To: [email protected] Subject: Re: Scan performance on a big table as combination of multiple logic tables Out of curiosity, what do you perceive as the benefit to having only one table? Are there reasons that you think one table would perform better than a few? If you're splitting data within a table because you'd otherwise have millions of tables, I understand that and would concur with Vladimir's approach below. However, if you're really looking at 10 tables versus one table, it seems like HBase is built exactly to make that work well (rather than having to make all sorts of application level code to do what HBase already does). thanks, Jacques On Wed, Feb 15, 2012 at 1:57 PM, Pan, Thomas <[email protected]> wrote: > > Since Hbase is tailored to handle one table very well, we are thinking to > put multiple tables into one big table but on different column family sets. > Our use case is full table scan against single column value filters. As > records from different "logical tables" are at different column families, > could we speed up the scan performance by simply checking the column family > referenced by these single column value filters first before really going > through all the underlying K-V pairs? It would be great if the Hbase code > is already coded that way. > > > $0.02, > Thomas > > Confidentiality Notice: The information contained in this message, including any attachments hereto, may be confidential and is intended to be read only by the individual or entity to whom this message is addressed. If the reader of this message is not the intended recipient or an agent or designee of the intended recipient, please note that any review, use, disclosure or distribution of this message or its attachments, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or [email protected] and delete or destroy any copy of this message and its attachments.
