Depends of course a lot on how many tenants you have. Hopefully the new off heap memtables is 1.0 may help as well as java gc on large heaps is getting a much bigger issue than memory cost.
Regards, Terje On 25 Aug 2011, at 14:20, Himanshi Sharma <[email protected]> wrote: > > I am working on similar sort of stuff. As per my knowledge, creating keyspace > for each tenant would impose lot of memory constraints. > > Following Shared Keyspace and Shared Column families would be a better > approach. And each row in CF could be referred by tenant_id as row key. > And again it depends on the type of application. > > Hey this is just a suggestion, m not completely sure.. :) > > > Himanshi Sharma > > > > > From: Guofeng Zhang <[email protected]> > To: [email protected] > Date: 08/25/2011 10:38 AM > Subject: For multi-tenant, is it good to have a key space for each > tenant? > > > > > I wonder if it is a good practice to create a key space for each tenant. Any > advice is appreciated. > > Thanks > > > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > >
