Revisiting 1M Writes per second
techblog.netflix.com
Revisiting 1M Writes per second
1–10 of 40 posts
Re: Revisiting 1M Writes per second
#2Here's some performance notes on the latest (2.1rc4): http://www.datastax.com/dev/blog/cassandra-2-1-now-over-50-f...
Re: Revisiting 1M Writes per second
#3I know I can divine it from the parameters to stress, but I have no idea if the row keys generated by different clients overlap and I don't know the default number of columns nor their size.
I think it's also important in this kind of benchmark to describe the distribution of access especially for a read intensive benchmark. Without that you really don't know what your are looking at. I am a fan of scrambled Zipfian.
Re: Revisiting 1M Writes per second
#4Re: Revisiting 1M Writes per second
#5This is running Cassandra 1.2.x which is over 18 months old. Here's some performance notes on the latest (2.1rc4): http://www.datastax.com/dev/blog/cassandra-2-1-now-over-50-f...
Re: Revisiting 1M Writes per second
#6http://www.youtube.com/watch?v=c12cYAUTXXs
That's 'Billion' with a 'B': Scaling to the Next Level at WhatsApp
(that walk title was create before the acquisition and was mean to imply message count, after the acquisition it got a secondary meaning).
The one thing that is fascinating about it, is how small their team was compared to the volume and complexity of the operation.
Re: Revisiting 1M Writes per second
#7Re: Revisiting 1M Writes per second
#8I wonder where the term sidecar originated from and what is the precise definition? Is this something invented by the netflix OSS people or does it predate that?
Re: Revisiting 1M Writes per second
#9Re: Revisiting 1M Writes per second
#10I wonder where the term sidecar originated from and what is the precise definition? Is this something invented by the netflix OSS people or does it predate that?
It's from here: https://www.google.com/search?q=motorcycle+sidecar&source=ln...