recommended. If it works for you, great,
> but if not, don't say you weren't warned.
>
> Disabling of slab allocation is an expert-only feature - its use is
> generally an anti-pattern, not recommended.
>
> -- Jack Krupansky
>
> On Sun, Jun 21, 2015 at 10:55 PM, Arun
any ideas or advises?
On Mon, Jun 22, 2015 at 10:55 AM, Arun Chaitanya
wrote:
> Hello All,
>
> Now we settled on the following approach. I want to know if there are any
> problems that you foresee in the production environment.
>
> Our Approach: Use Off Heap Memory
&g
media.tumblr.com/5d0efca7288dc969c1ac4fc3d36e0151/tumblr_inline_mzvj254quj1rd24f4.png
>
> About an order of magnitude difference in performance.
>
> Jon
>
> On Mon, Jun 1, 2015 at 7:20 PM Arun Chaitanya
> wrote:
>
>> Thanks Jon and Jack,
>>
>> > I strongl
rs", but did you mean 10 nodes? You might want
> to consider a model where you do indeed have multiple clusters, where each
> handles a fraction of the tenants, since there is no need for separate
> tenants to be on the same cluster.
>
>
> -- Jack Krupansky
>
> On Tue,
LAs or many different developers with different managers with
> different goals such as SLAs?
>
> When you say multi-tenant, are you simply saying that each of your
> organization's customers has their data segregated, or does each customer
> have direct access to the cluster?
&g
stored data volume also.
>
> Also hard to answer your questions without an idea of read/write load
> system wide, and indeed distribution across tenants.
>
>
> On May 26, 2015, at 10:32 PM, Arun Chaitanya
> wrote:
>
> Good Day Everyone,
>
> I am very happy with th
Good Day Everyone,
I am very happy with the (almost) linear scalability offered by C*. We had
a lot of problems with RDBMS.
But, I heard that C* has a limit on number of column families that can be
created in a single cluster.
The reason being each CF stores 1-2 MB on the JVM heap.
In our use ca
