cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ertio Lew <ertio...@gmail.com>
Subject Re: Using cassandra at minimal expenditures
Date Thu, 01 Mar 2012 10:26:09 GMT
expensive :-) I was expecting to start with 2GB nodes, if not 1GB for
intial.

On Thu, Mar 1, 2012 at 3:43 PM, aaron morton <aaron@thelastpickle.com>wrote:

> As others said, depends on load and traffic and all sorts of thins.
>
> if you want a number, 4Gb would me a reasonable minimum IMHO. (You may get
> by with less).  8Gb is about the tops.
> Any memory not allocated to Cassandra  will be used to map files into
> memory.
>
> If you can get machines with 8GB ram thats a reasonable start.
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 1/03/2012, at 1:16 AM, Maki Watanabe wrote:
>
> Depends on your traffic :-)
>
> cassandra-env.sh will try to allocate heap with following formula if
> you don't specify MAX_HEAP_SIZE.
> 1. calculate 1/2 of RAM on your system and cap to 1024MB
> 2. calculate 1/4 of RAM on your system and cap to 8192MB
> 3. pick the larger value
>
> So how about to start with the default? You will need to monitor the
> heap usage at first.
>
> 2012/2/29 Ertio Lew <ertiop93@gmail.com>:
>
> Thanks, I think I don't need high consistency(as per my app requirements)
> so
>
> I might be fine with CL.ONE instead of quorum, so I think  I'm probably
>
> going to be ok with a 2 node cluster initially..
>
>
> Could you guys also recommend some minimum memory to start with ? Of course
>
> that would depend on my workload as well, but that's why I am asking for
> the
>
> min
>
>
>
> On Wed, Feb 29, 2012 at 7:40 AM, Maki Watanabe <watanabe.maki@gmail.com>
>
> wrote:
>
>
> If you run your service with 2 node and RF=2, your data will be
>
> replicated but
>
> your service will not be redundant. ( You can't stop both of nodes )
>
>
> If your service doesn't need strong consistency ( allow cassandra returns
>
> "old" data after write, and possible write lost ), you can use CL=ONE
>
> for read and write
>
> to keep availability.
>
>
> maki
>
>
>
>
>
>
> --
> w3m
>
>
>

Mime
View raw message