From 18ef5fe1c4aba03d2458e88fbff1c847be23322c Mon Sep 17 00:00:00 2001 From: Louis Chatriot Date: Tue, 11 Jun 2013 14:06:59 +0200 Subject: [PATCH] Update README.md --- README.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/README.md b/README.md index 31d5285..f5b79d9 100644 --- a/README.md +++ b/README.md @@ -328,10 +328,7 @@ db.insert({ somefield: 'nedb' }, function (err) { ## Performance ### Speed -**NeDB is not intended to be a replacement of large-scale databases such as MongoDB!** Its goal is to provide you with a clean and easy way to query data and persist it to disk, for web applications that do not need lots of concurrent connections, for example a continuous integration and deployment server and desktop applications built with Node Webkit. - -As such, it was not designed for speed. That said, it is still pretty fast on the expected datasets, especially if you use indexing. On my machine (3 years old, no SSD), with a collection -containing 10,000 documents, with indexing and no pipelining: +NeDB is not intended to be a replacement of large-scale databases such as MongoDB, and as such was not designed for speed. That said, it is still pretty fast on the expected datasets, especially if you use indexing. On my machine (3 years old, no SSD), with a collection containing 10,000 documents, with indexing and no pipelining: * Insert: **5,950 ops/s** * Find: **41,320 ops/s** * Update: **4,490 ops/s**