On Mon, Dec 10, 2018 at 3:23 PM Riccardo Ferrari wrote:
>
> By "small" I mean that currently I have a 6x m1.xlarge instances running
> Cassandra 3.0.17. Total amount of data is around 1.5TB spread across couple
> of keypaces wih RF:3.
>
> Over time few things happened/became clear including:
>
>
Thanks for the feedback.
By "small" I mean that currently I have a 6x m1.xlarge instances running
Cassandra 3.0.17. Total amount of data is around 1.5TB spread across couple
of keypaces wih RF:3.
Over time few things happened/became clear including:
- increase amount of ingested data
- m1.
On Mon, Dec 10, 2018 at 12:20 PM Riccardo Ferrari
wrote:
> I am wondering what instance type is best for a small cassandra cluster on
> AWS.
>
Define "small" :-D
> Actually I'd like to compare, or have your opinion about the following
> instances:
>
>- r5*d*.xlarge (4vCPU, *19*ecu, 32GB ra
I'm not really a hardware performance guy, still looking at that with
cassandra. I use 2 t.large instances with reserved pricing, which saves
about 80% on costs if you pay for 1 year.
On Mon, Dec 10, 2018 at 12:20 PM Riccardo Ferrari
wrote:
> Hi list!
>
> I am wondering what instance type is be
Hi list!
I am wondering what instance type is best for a small cassandra cluster on
AWS.
Actually I'd like to compare, or have your opinion about the following
instances:
- r5*d*.xlarge (4vCPU, *19*ecu, 32GB ram and 1 NVMe instance store 150GB)
- Need to attach a 600/900GB ESB
- i3
