Sent from my iPhone
On 27.09.2010, at 19:30, Marc Canaleta wrote:
> What do you mean by "running live"? I am also planning to use cassandra on
> EC2 using small nodes. Small nodes have 1/4 cpu of the large ones, 1/4 cost,
> but I/O is more than 1/4 (amazon does not give explicit I/O numbers.
In my opinion it's the wrong approach when so ask how to migrate from MySQL to
Cassandra from a database level view. The lack of joins in NoSQL should lead to
think about what you wanna get out of your persistent storage and afterwards
think about how to migrate and most of the time how to denor
10 writes / second could even be done with every sql/nosql solution, even with
plain files.
So I think the storage choosen should be the one optimized for the queries you
wanna have.
Sent from my iPhone
On 06.08.2010, at 05:54, Sal Fuentes wrote:
> Would you care to elaborate?
>
> On Thu, A
a
> mysql join. Hope i explained the point.
>
> Cheers,
> Deepu.
>
> On Tue, Jul 13, 2010 at 11:38 AM, Michael Dürgner wrote:
> Are your PVs mostly read or write? As if they are read, I'd think you
> wouldn't need a Cassandra like storage which is tuned towar
Are your PVs mostly read or write? As if they are read, I'd think you wouldn't
need a Cassandra like storage which is tuned towards writes.
Am 12.07.2010 um 23:40 schrieb Sandeep Kalidindi at PaGaLGuY.com:
> well we were going down constantly with VB running on 3-4 dedicated servers
> due to h
Have you done some testing with small nodes already? Because from what we saw
trying to run IO bound services on small instances is, that their IO
performance is really bad compared to other instance types as you can read in
several blogs.
Would be interesting to hear, if a Cassandra cluster ca