News for hackers. Stuff that matters.
Re:How to choose an in-memory NoSQL solution: Performance me... by aps-sids on Wednesday December 30, 2015 @01:50PM (#10813558)
I'm quite surprised to see that there's no Aerospike in this comparison.
Re:How to choose an in-memory NoSQL solution: Performance me... by hmottestad on Wednesday December 30, 2015 @02:55PM (#10813958)
Re:How to choose an in-memory NoSQL solution: Performance me... by karmakaze on Wednesday December 30, 2015 @03:04PM (#10814013)
Similarly, I was hoping to find VoltDB in the mix.
Re:How to choose an in-memory NoSQL solution: Performance me... by rvncerr on Tuesday January 12, 2016 @07:28AM (#10886987)
I'll try to benchmark it soon. Thank you!
Re:How to choose an in-memory NoSQL solution: Performance me... by karmakaze on Wednesday December 30, 2015 @05:36PM (#10814865)
Why downvote? How is VoltDB not relevant here?
Re:How to choose an in-memory NoSQL solution: Performance me... by drdaeman on Wednesday December 30, 2015 @10:03PM (#10815874)
No idea (I haven't voted here at all), but maybe someone didn't want to make this a long thread naming myriad of NoSQL databases out there?
Re:How to choose an in-memory NoSQL solution: Performance me... by rvncerr on Monday January 11, 2016 @04:32AM (#10879792)
This is only a first try. I'm going to make another review of a large number of NoSQL solutions soon. Aerospike will be observed there.
Re:How to choose an in-memory NoSQL solution: Performance me... by no1youknowz on Wednesday December 30, 2015 @02:09PM (#10813677)
Agreed. It's pretty trivial to overwhelm a Redis instance. For ad serving scenarios at high traffic scenarios Aerospike is really where it's at.
Re:How to choose an in-memory NoSQL solution: Performance me... by thezilch on Wednesday December 30, 2015 @02:22PM (#10813767)
Unlikely you are going to overwhelm Redis in a non-deterministic fashion. What do you even mean by overwhelm?

The post only concerns itself with in-memory workloads; I don't think Aerospike is competition in this space, while their advantage is against workloads working against SSD backed datasets. "After Google published a blog post “Cassandra Hits One Million Writes Per Second on Google Compute Engine” – using 300 nodes, we followed the same steps and documented how Aerospike Hits One Million Writes Per Second With Just 50 Nodes On Google Compute Engine. [...] Aerospike on SSD is very comparable to that of RAM. At 100% write, the SSDs are able to sustain 226,000 transactions per second compared to 239,000 for RAM." [0] Redis would have no problem hitting 250K IOPS on just a single core provided by GCE (or AWS EC2 or similar).

[0] http://www.aerospike.com/resource/aerospike-soars-in-the-goo...

Re:How to choose an in-memory NoSQL solution: Performance me... by itamarhaber on Wednesday December 30, 2015 @02:52PM (#10813940)
Redis needs only two nodes on GCE to deliver 1M writes per second: https://redislabs.com/blog/nosql-bar-datastax-aerospike-couc...
Re:How to choose an in-memory NoSQL solution: Performance me... by itamarhaber on Wednesday December 30, 2015 @02:56PM (#10813971)
A single Redis instance uses a single CPU core so yeah, hitting the its limits (no matter how high) is always a possibility. OTOH, there's always the possibility for sharding and clustering a Redis database to scale it up 'n out, thus making "overwhelming" it less trivial.