Sizing ScyllaDB for migrating an existing DynamoDB Table

[johan...@gmail.com]

Would like to get advise on what's the recommended AWS instance sizes for a cluster where we will migrate a few DynamoDB tables to. Currently the busiest table, while less than a GB in size, consumes a lot of read capacity units - 183M consumed RCUs on the busiest hour, with 5M happening in the busiest minute.

Yeah, there's a lot to be done on the app to lower this read utilization, but our target is to move it to ScyllaDB Alternator to hopefully drastically reduce expenses then rewrite the app to use ScyllaDB without Alternator.

Thanks!

Johann

[Eyal Gutkind]

Hi Johann,

I'd start with 3 nodes of i3.2xlarge. 

We do not know the actuals on the peak transactions per second and target latency budget. 
But, it will be safe to say you can start with the i3.2xlarge. Do install Scylla monitoring on a separate node, and track the CPU/IO consumptions during your peak times.

HTH,

Eyal

--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/959a5e80-ebac-42b9-b855-fe3e50470dabn%40googlegroups.com.

[johan...@gmail.com]

Thanks!