diff options
| author | Ben Johnson <benbjohnson@yahoo.com> | 2015-03-27 16:14:54 -0600 |
|---|---|---|
| committer | Ben Johnson <benbjohnson@yahoo.com> | 2015-03-27 16:14:54 -0600 |
| commit | 73b849dfc20bbdafc9129dde690c68cde105be1a (patch) | |
| tree | 0b9c3099d7f331a9e8ed7d5a08845b5eaeb458f5 | |
| parent | Merge pull request #334 from funkygao/master (diff) | |
| parent | Add link to page reclamation comment. (diff) | |
| download | dedo-73b849dfc20bbdafc9129dde690c68cde105be1a.tar.gz dedo-73b849dfc20bbdafc9129dde690c68cde105be1a.tar.xz | |
Merge pull request #336 from boltdb/reclamation-docs
README
| -rw-r--r-- | README.md | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -550,6 +550,17 @@ Here are a few things to note when evaluating and using Bolt: However, this is expected and the OS will release memory as needed. Bolt can handle databases much larger than the available physical RAM. +* Because of the way pages are laid out on disk, Bolt cannot truncate data files + and return free pages back to the disk. Instead, Bolt maintains a free list + of unused pages within its data file. These free pages can be reused by later + transactions. This works well for many use cases as databases generally tend + to grow. However, it's important to note that deleting large chunks of data + will not allow you to reclaim that space on disk. + + For more information on page allocation, [see this comment][page-allocation]. + +[page-allocation]: https://github.com/boltdb/bolt/issues/308#issuecomment-74811638 + ## Other Projects Using Bolt |