warptangent fd73d9cc3a Check and resize if needed at batch transaction start ... This currently only affects blockchain_import and blockchain_converter. When the number of blocks expected for the batch transaction is provided, make an estimate of the DB space needed. If not enough free space remains, resize the DB. The estimate is made based on: - the average size of the last 500 blocks, or if larger, a min. block size of 4k - a factor for the expanded size a block occupies in the DB across the sub-dbs/tables - a safety factor (1.7) to allow for a "reasonable" average block size increase over the batch Increase the DB size by whichever is greater: the estimated size needed or a minimum increase size, currently 128 MB. The conservative factors in the estimate help in testing that the resize occurs when needed, and without gratuitous size increases. For common use, the safety factor and minimum increase size could reasonably be increased. For testing, setting DEFAULT_MAPSIZE (blockchain_db/lmdb/db_lmdb.h) to 1 << 27 (128 MB) and recompiling will ensure DB resizes take place sooner and more frequently.		2015-07-12 00:51:39 -07:00
..
berkeleydb	Optionally allow DB to know expected number of blocks at batch transaction start	2015-07-11 23:54:12 -07:00
lmdb	Check and resize if needed at batch transaction start	2015-07-12 00:51:39 -07:00
blockchain_db.cpp	blockchain_db: add a few const	2015-05-27 19:16:37 +01:00
blockchain_db.h	Optionally allow DB to know expected number of blocks at batch transaction start	2015-07-11 23:54:12 -07:00
CMakeLists.txt	Only compile BerkeleyDB as an option in non-static	2015-04-07 15:02:20 -04:00
db_types.h	Steps toward multiple dbs available -- working	2015-03-25 12:09:44 -04:00