weaviate_go_memstats_heap_inuse_size

The number of heap bytes that are in use in the Weaviate instance

Dimensions:None

Technical Annotations (18)

Configuration Parameters (5)

GOMEMLIMITrecommended: 10-20% of total memory (e.g., 10GiB for 100GiB nodes)

Controls Go garbage collector soft memory limit; 50GiB on 100GiB nodes (50%) is too high

vectorCacheMaxObjectsrecommended: 500000000000

Half the default value to reduce memory pressure

cpuPercentagerecommended: not specified

Backup parameter to limit CPU usage during backup operations

GOGCrecommended: 100 (default) or lower for memory-constrained environments

Controls Go garbage collection frequency; affects memory/CPU tradeoff

ASYNC_REPLICATION_HASHTREE_HEIGHTrecommended: reduce for many tenants, increase for very large collections

Controls memory footprint vs efficiency of diff identification

Technical References (13)

S3 backupcomponentBACKUP_S3_BUCKETconfigurationcollectioncomponentschema structureconceptvectorsconceptGOGCcomponentGOMEMLIMITcomponenthash treecomponenttenantconceptmulti-tenant collectionconceptHNSW indexcomponentminio-gocomponentmulti-part uploadprotocol

Related Insights (8)

Memory increases during S3 backup and never returns to baselinecritical

▸

Heap memory not dropping near GOMEMLIMIT indicates resource exhaustionwarning

▸

Memory formula underprovisioning causes cluster failure with multi-tenancy and updatescritical

▸

Memory usage more than doubles after upgrading Weaviate 1.18 to 1.25warning

▸

GOGC and GOMEMLIMIT misconfiguration causes replication timeoutswarning

▸

High memory footprint in multi-tenant deploymentswarning

▸

Inefficient CPU-to-memory ratio degrades vector workload performancewarning

▸

Unconfigured MinIO part size causes memory bloat during backupswarning

▸