News for hackers. Stuff that matters.

rvncerr

rvncerr on Hacker News

Re:How to choose an in-memory NoSQL solution: Performance measuring 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 measuring on Tuesday January 12, 2016 @07:26AM (#10886974)
I've used my simple Memcached module, not Couchbase SDK.
Re:How to choose an in-memory NoSQL solution: Performance measuring on Tuesday January 12, 2016 @07:12AM (#10886926)
I haven't tried PostgreSQL as an in-memory solution, but in my another benchmark it has reached a good performance in comparison with other on-disk solutions. Thank you! I've scheduled benchmark of PostgreSQL in RAM.
Re:How to choose an in-memory NoSQL solution: Performance measuring on Tuesday January 12, 2016 @07:07AM (#10886909)
I will try it. Thank you!
Re:How to choose an in-memory NoSQL solution: Performance measuring on Tuesday January 12, 2016 @07:06AM (#10886902)
Underperforming might be caused by my YCSB memcached driver... I'll revise it. Memcached utilized all CPUs during the benchmark.

P.S. All VM images are open, you can repeat the benchmark if you wish.

Re:How to choose an in-memory NoSQL solution: Performance measuring 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 measuring on Sunday January 03, 2016 @10:14PM (#10833827)
Yes, it is. When I was running the test, CouchBase 4.x hasn't been released.
Re:How to choose an in-memory NoSQL solution: Performance measuring on Sunday January 03, 2016 @10:05PM (#10833803)
No, I ran two instances close to each other (in one DC).

For example, Tarantool and CouchBase were installed on nosql-1 instance and YCSB client on nosql-2 (There are links to *.vhd files in the article).