From 96007220db45bde835f75c62a323621e55516fe0 Mon Sep 17 00:00:00 2001 From: Louis Chatriot Date: Fri, 17 May 2013 15:04:26 +0200 Subject: [PATCH] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 27e5c0a..53701bb 100644 --- a/README.md +++ b/README.md @@ -163,7 +163,9 @@ db.remove({ system: 'solar' }, { multi: true }, function (err, numRemoved) { ## Performance ### Speed -It is pretty fast on the kind of datasets it is designed for (10,000 +**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 applications that do not need lots of concurrent connections, for example a continuous integration and deployment server. + +As such, it was not designed for speed. That said, it is still pretty fast on the expected datasets (10,000 documents max). On my machine (3 years old, no SSD), with a collection containing 10,000 documents: * An insert takes 0.1ms