|
|
|
|
|
by devdazed
5636 days ago
|
|
I wouldn't say it's completely useless as it shows that Mongo is faster in a single threaded process, using the most popular ruby client of each system. If I were writing a high-concurrency multi-threaded system to handle millions of keys at a time, Ruby would not be my first choice by far. |
|
No, it doesn't. You ran 100k increments on one key and divided by time ONCE and printed the result.
Plus this was on your Macbook Pro, which is probably running a mail client, Twitter client, web browser, and hundreds of other things that could have affected the times.
Graphing the response times for each increment would be a good way to start looking at what the data really shows, instead of going by a single opaque, fairly useless number.