Ops you're right, off by 10.
should be 12,800 write and 3,200 read.
Will also take the opportunity again to say this are just "some numbers" that
may help when understanding how your app will behave when moving to new HW. And
that there are a lot of other things the nodes have to do (like comp
Aaron,
How did you get to 1280 writes/sec? Counting 64 writers each taking 5ms for a
write cycle, assuming real parallel access with no speed hits, I get 12,800
writes/sec. Am I missing something?
From Jose's iPhone
On Mar 24, 2011, at 2:52 PM, aaron morton wrote:
> Big old guess of somethi
Big old guess of something in the 1000's.
Try benchmarking your work load and plug the numbers (my 5m is pretty high)
in...
- 8 cores * 8 writers per core = 64 if each write request takes 5ms = 1280 max
per sec
- 1 spindle * 16 readers per spindle = 16 readers if each read request takes
5ms
Thanks for the tips on the replication factor. Any thoughts on the
number of nodes in a cluster to support an RF=3 with a workload of 400
ops/sec (4-8K sized rows, 50/50 read/write)? Based on the "sweet
spot" hardware referenced in the wiki (8-core, 16-32GB RAM), what kink
of ops/sec could I reas
It really does depend on what your workload is like, and in the end will
involve a certain amount of fudge factor.
http://wiki.apache.org/cassandra/CassandraHardware provides some guidance.
http://wiki.apache.org/cassandra/MemtableThresholds can be used to get a rough
idea of the memory requ
I'm going through the process of specing out the hardware for a
Cassandra cluster. The relevant specs:
- Support 460 operations/sec (50/50 read/write workload). Row size
ranges from 4 to 8K.
- Support 29 million objects for the first year
- Support 365 GB storage for the first year, based on Cassa
