Far from expert opinion, however one configuration I have seen talked about is 3 x m1.xlarge in AWS.
I have tested 4 x m1.xlarge and 4 x m1.large. The m1.xlarge was fine for out tests (we were hitting it pretty hard), the m1.large was eratic - from that I took way that you either need to give Cassandra sufficient resources or know how to tune properly (I don't) cheers On Tue, Sep 24, 2013 at 2:17 AM, Tim Dunphy <bluethu...@gmail.com> wrote: > Hello, > > I am running Cassandra 2.0 on a 2gb memory 10 gb HD in a virtual "cloud" > environment. It's supporting a php application running on the same node. > > Mostly this instance runs smoothly but runs low on memory. Depending on > how much the site is used, the VM will swap out sometimes excessively. > > I realize this setup may not be enough to support a cassandra instance. > > I was wondering if there were any "recommended hardware specs" someone > could point me to for both physical and virtual (cloud) type environments. > > Thank you, > Tim > Sent from my iPhone -- *Franc Carter* | Systems architect | Sirca Ltd <marc.zianideferra...@sirca.org.au> franc.car...@sirca.org.au | www.sirca.org.au Tel: +61 2 8355 2514 Level 4, 55 Harrington St, The Rocks NSW 2000 PO Box H58, Australia Square, Sydney NSW 1215
