The total memory, in bytes, allocated and administered by Vector Server memory pooling. It includes the total memory used by currently running sessions and global server memory. It includes memory.updates_allocated, memory.committed_transactions, memory.index_allocated.

The maximum allowed amount of physical memory, in bytes. If this threshold is reached, some queries will stop working. It is configured with the [memory] max_memory_size configuration parameter.

The maximum amount of memory, in bytes, allocated at one single moment by running sessions during the lifetime of the server.

This information is useful for dimensioning the system. If this amount is close to the maximum allowed amount of physical memory, the server may return out-of-memory (OOM) errors. Consider changing the maximum allowed amount of physical memory on the [memory]max_memory_size configuration parameter and possibly adding more physical memory to the server.

The amount of virtual memory, in bytes, allocated by the currently running queries. In most cases, this amount is higher than the amount of physical memory. It indicates the address space the server is using rather than an amount of allocated memory. This memory is allocated only when the server will use it, and is then displayed in memory.memcontext_allocated. The server allocates more address space than memory to avoid memory fragmentation and copying when certain memory areas grow. You can influence this behavior with the [memory]max_overalloc configuration parameter.

The maximum allowed amount of allocated virtual memory, in bytes

The maximum amount of virtual memory, in bytes, allocated at one single moment by running sessions during the lifetime of the server. This value will always be lower than the maximum allowed amount of allocated virtual memory (memory.memcontext_virtual_maximum).

The total memory, in bytes, allocated for in-memory indexes (min-max indexes and secondary indexes, if supported)

The total memory, in bytes, used by memory-buffered updates of the committed transactions. The amount of this memory can be reduced by the automatic propagation mechanism (see Management of In-memory Updates on page 29). It can also be freed manually by issuing the statement MODIFY...TO COMBINE; COMMIT; on tables with in-memory updates, which will propagate the in-memory updates to disk (see Propagate In-memory Updates to Disk on page 105).

The maximum amount of memory, in bytes, that can be used by memory-buffered updates. If memory.update_allocated reaches this limit, propagation (see Management of In-memory Updates on page 29) is triggered. If propagation is not successful, and the limit is reached, the memory-buffered updates may stop being accepted.

The total memory, in bytes, used by stored committed transactions. Vector keeps some information about a transaction in memory as long as any overlapping transaction is still running. This information is needed for potential conflict resolution. When this value becomes too high, the user must commit or abort some or all current sessions to free the memory occupied by the committed transactions. A typical cause for this value becoming high is a single old transaction that is still active.

The total size, in bytes, of the buffer pool (disk block cache)

(Linux only) Miscellaneous memory allocated, in bytes, outside the memory pooling.

The disk block size used by this database. It is configured with the [cbm] block_size configuration parameter.

The group size used by this database. It is configured with the [cbm] group_size configuration parameter.

The number of blocks used in total over all files and all locations

The size of a buffer pool (disk data cache), in blocks. You can compute the total allowed physical size by multiplying this value by bm.block_size. This value is a sum of bm.bufferpool_free_blocks and bm.bufferpool_used_blocks.

The number of blocks in the buffer pool that can be used for new data

The number of blocks in the buffer pool that are currently locked by queries. This includes only blocks that are currently being used by scans and write to disk operations, which typically operate on only one block per column at a time. For statistics on cached data, see bm.bufferpool_cached_blocks.

The number of blocks in the buffer pool that contain cached data from disk

The number of currently running queries

Current size, in bytes, of the transaction log file

Size, in bytes of the transaction log file at which the system tries to compact it

The port used for internal communication between the client and server

The system process ID of the x100_server (iix100) process