[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Assembly: Db4objects.Db4o (in Db4objects.Db4o.dll)
tuning feature only: reserves a number of bytes in database files.
Namespace: Db4objects.Db4o.Config
Assembly: Db4objects.Db4o (in Db4objects.Db4o.dll)
Syntax
Visual Basic (Declaration) |
---|
Sub ReserveStorageSpace ( _ byteCount As Long _ ) |
C# |
---|
void ReserveStorageSpace ( long byteCount ) |
Visual C++ |
---|
void ReserveStorageSpace ( long long byteCount ) |
Parameters
- byteCount
- System.Int64
the number of bytes to reserve
Remarks
tuning feature only: reserves a number of bytes in database files.
The global setting is used for the creation of new database files. Continous calls on an ObjectContainer Configuration context (see Db4objects.Db4o.Ext.IExtObjectContainer.Configure ) will continually allocate space.
The allocation of a fixed number of bytes at one time makes it more likely that the database will be stored in one chunk on the mass storage. Less read/write head movevement can result in improved performance.
Note:
Allocated space will be lost on abnormal termination of the database engine (hardware crash, VM crash). A Defragment run will recover the lost space. For the best possible performance, this method should be called before the Defragment run to configure the allocation of storage space to be slightly greater than the anticipated database file size.
Default configuration: 0
The global setting is used for the creation of new database files. Continous calls on an ObjectContainer Configuration context (see Db4objects.Db4o.Ext.IExtObjectContainer.Configure ) will continually allocate space.
The allocation of a fixed number of bytes at one time makes it more likely that the database will be stored in one chunk on the mass storage. Less read/write head movevement can result in improved performance.
Note:
Allocated space will be lost on abnormal termination of the database engine (hardware crash, VM crash). A Defragment run will recover the lost space. For the best possible performance, this method should be called before the Defragment run to configure the allocation of storage space to be slightly greater than the anticipated database file size.
Default configuration: 0