=E2=80=9C/Insert-heavy workload=
s will actually be CPU-bound in Cassandra before being
memory-bound/=E2=80=9D

However, from reading the documentation(<=
a href=3D"http://www.datastax.com/docs/1.2/dml/about_writes" rel=3D"nofollo=
w" link=3D"external" target=3D"_blank">http://www.datastax.com/docs/1.2/dml=
/about_writes) it seems the disk is the
real bottleneck in Writes rather than the CPU. This is because everything i=
s*first *written to the commit log *on disk*. Any thoughts??