mirror of https://github.com/etcd-io/bbolt.git
Add caveat regarding endianness of data files as suggested by Raphael Geronimi.
parent
fd65d6c954
commit
da700e8fdb
|
@ -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
|
However, this is expected and the OS will release memory as needed. Bolt can
|
||||||
handle databases much larger than the available physical RAM.
|
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
|
* 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
|
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
|
of unused pages within its data file. These free pages can be reused by later
|
||||||
|
|
Loading…
Reference in New Issue