Collapse All Expand All Code: All Code: Multiple Code: C# Code: Visual Basic Code: Visual C++

C#
Visual Basic
Visual C++

Berkeley DB .NET API Documentation
LogConfig..::.BufferSize Property
LogConfig Class See Also Send Feedback

The size of the in-memory log buffer, in bytes.

Namespace: BerkeleyDB
Assembly: libdb_dotnet181 (in libdb_dotnet181.dll) Version: 18.1.32.0

# Syntax

C#
    public uint BufferSize { get; set; }

Visual Basic (Declaration)
    Public Property BufferSize As UInteger

Visual C++
    public:
    property unsigned int BufferSize {
    	unsigned int get ();
    	void set (unsigned int value);
    }

# Remarks

When the logging subsystem is configured for on-disk logging, the default size of the in-memory log buffer is approximately 32KB. Log information is stored in-memory until the storage space fills up or transaction commit forces the information to be flushed to stable storage. In the presence of long-running transactions or transactions producing large amounts of data, larger buffer sizes can increase throughput.

When the logging subsystem is configured for in-memory logging, the default size of the in-memory log buffer is 1MB. Log information is stored in-memory until the storage space fills up or transaction abort or commit frees up the memory for new transactions. In the presence of long-running transactions or transactions producing large amounts of data, the buffer size must be sufficient to hold all log information that can accumulate during the longest running transaction. When choosing log buffer and file sizes for in-memory logs, applications should ensure the in-memory log buffer size is large enough that no transaction ever spans the entire buffer, and avoid a state where the in-memory buffer is full and no space can be freed because a transaction that started in the first log "file" is still active.

If the database environment already exists when Open(String, DatabaseEnvironmentConfig) is called, the value of BufferSize will be ignored.

# See Also

LogConfig Class
BerkeleyDB Namespace