diff options
| author | Ben Johnson <benbjohnson@yahoo.com> | 2015-12-05 20:28:01 -0700 |
|---|---|---|
| committer | Ben Johnson <benbjohnson@yahoo.com> | 2015-12-05 20:28:01 -0700 |
| commit | b34b35ea8d06bb9ae69d9a349119252e4c1d8ee0 (patch) | |
| tree | 289ff085147f0196149bc21f7a74228a258fb783 | |
| parent | Merge pull request #463 from rhcarvalho/fix-stats (diff) | |
| parent | README (diff) | |
| download | dedo-b34b35ea8d06bb9ae69d9a349119252e4c1d8ee0.tar.gz dedo-b34b35ea8d06bb9ae69d9a349119252e4c1d8ee0.tar.xz | |
Merge pull request #467 from boltdb/readme-coalescer
README
| -rw-r--r-- | README.md | 5 |
1 files changed, 2 insertions, 3 deletions
@@ -588,9 +588,8 @@ It's important to pick the right tool for the job and Bolt is no exception. Here are a few things to note when evaluating and using Bolt: * Bolt is good for read intensive workloads. Sequential write performance is - also fast but random writes can be slow. You can add a write-ahead log or - [transaction coalescer](https://github.com/boltdb/coalescer) in front of Bolt - to mitigate this issue. + also fast but random writes can be slow. You can use `DB.Batch()` or add a + write-ahead log to help mitigate this issue. * Bolt uses a B+tree internally so there can be a lot of random page access. SSDs provide a significant performance boost over spinning disks. |