From 03568094bcd4c93784207e700ab7453761f8fb86 Mon Sep 17 00:00:00 2001 From: Louis Chatriot Date: Thu, 5 Nov 2015 10:27:50 +0100 Subject: [PATCH] Update README.md --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 45c0215..538c2fe 100644 --- a/README.md +++ b/README.md @@ -603,10 +603,10 @@ As of v0.11, NeDB is also persistent on the browser. To use this, simply create ## Performance ### Speed 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: -* Insert: **5,950 ops/s** -* Find: **25,440 ops/s** -* Update: **4,490 ops/s** -* Remove: **6,620 ops/s** +* Insert: **10,680 ops/s** +* Find: **43,290 ops/s** +* Update: **8,000 ops/s** +* Remove: **11,750 ops/s** You can run these simple benchmarks by executing the scripts in the `benchmarks` folder. Run them with the `--help` flag to see how they work.