From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/am_misc_dbsizes.html | 79 ++++++++++++++++---------- 1 file changed, 50 insertions(+), 29 deletions(-) (limited to 'docs/programmer_reference/am_misc_dbsizes.html') diff --git a/docs/programmer_reference/am_misc_dbsizes.html b/docs/programmer_reference/am_misc_dbsizes.html index 2cae3130..dac7a08e 100644 --- a/docs/programmer_reference/am_misc_dbsizes.html +++ b/docs/programmer_reference/am_misc_dbsizes.html @@ -14,7 +14,7 @@ -

The largest database file that Berkeley DB can handle depends on the page size -selected by the application. Berkeley DB stores database file page numbers as -unsigned 32-bit numbers and database file page sizes as unsigned 16-bit -numbers. Using the maximum database page size of 65536, this results in -a maximum database file size of 248 (256 terabytes). The -minimum database page size is 512 bytes, which results in a minimum -maximum database size of 241 (2 terabytes).

-

The largest database file Berkeley DB can support is potentially further limited -if the host system does not have filesystem support for files larger than -232, including the ability to seek to absolute offsets within -those files.

-

The largest key or data item that Berkeley DB can support is 232, -or more likely limited by available memory. Specifically, while key and -data byte strings may be of essentially unlimited length, any one of -them must fit into available memory so that it can be returned to the -application. As some of the Berkeley DB interfaces return both key and data -items to the application, those interfaces will require that any -key/data pair fit simultaneously into memory. Further, as the access -methods may need to compare key and data items with other key and data -items, it may be a requirement that any two key or two data items fit -into available memory. Finally, when writing applications supporting -transactions, it may be necessary to have an additional copy of any data -item in memory for logging purposes.

-

The maximum Btree depth is 255.

+

+ The largest database file that Berkeley DB can handle + depends on the page size selected by the application. Berkeley + DB stores database file page numbers as unsigned 32-bit + numbers and database file page sizes as unsigned 16-bit + numbers. Using the maximum database page size of 65536, this + results in a maximum database file size of + 248 (256 terabytes). The + minimum database page size is 512 bytes, which results in a + minimum maximum database size of + 241 (2 terabytes). +

+
+

Note

+

+ In order to store petabytes of data you can use + multiple database files. +

+
+

+ The largest database file Berkeley DB can support is + potentially further limited if the host system does not have + filesystem support for files larger than + 232, including the ability to + seek to absolute offsets within those files. +

+

+ The largest key or data item that Berkeley DB can support + is 232, or more likely limited by + available memory. Specifically, while key and data byte + strings may be of essentially unlimited length, any one of + them must fit into available memory so that it can be returned + to the application. As some of the Berkeley DB interfaces + return both key and data items to the application, those + interfaces will require that any key/data pair fit + simultaneously into memory. Further, as the access methods may + need to compare key and data items with other key and data + items, it may be a requirement that any two key or two data + items fit into available memory. Finally, when writing + applications supporting transactions, it may be necessary to + have an additional copy of any data item in memory for logging + purposes. +

+

+ The maximum Btree depth is 255. +

-- cgit v1.2.1