diff options
| author | Ben Johnson <benbjohnson@yahoo.com> | 2015-05-06 09:26:22 -0600 |
|---|---|---|
| committer | Ben Johnson <benbjohnson@yahoo.com> | 2015-05-06 09:26:22 -0600 |
| commit | da700e8fdb065b7e073700c9afa8369d4c60c674 (patch) | |
| tree | 619fb4625cb444cc1f165eb32681cc4b77568cd0 | |
| parent | Merge pull request #363 from benbjohnson/no-truncate (diff) | |
| download | dedo-da700e8fdb065b7e073700c9afa8369d4c60c674.tar.gz dedo-da700e8fdb065b7e073700c9afa8369d4c60c674.tar.xz | |
Add caveat regarding endianness of data files as suggested by Raphael Geronimi.
| -rw-r--r-- | README.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -550,6 +550,11 @@ 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. +* The data structures in the Bolt database are memory mapped so the data file + will be endian specific. This means that you cannot copy a Bolt file from a + little endian machine to a big endian machine and have it work. For most + users this is not a concern since most modern CPUs are little endian. + * 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 |