Technologies/Langfuse/langfuse.container.memory.utilization
LangfuseLangfuseMetric

langfuse.container.memory.utilization

Container memory utilization percentage
Dimensions:None
Available on:CloudWatchCloudWatch (1)
Interface Metrics (1)
CloudWatchCloudWatch
Memory utilization percentage for the container
Dimensions:None
Sources
langfuse.container.memory.utilizationdocs.aws.amazon.com

Technical Annotations (20)

Configuration Parameters (5)
NODE_OPTIONSrecommended: --max-old-space-size=<memory_in_mib>
Set to container memory limit to enable graceful pod termination
LANGFUSE_INGESTION_QUEUE_PROCESSING_CONCURRENCYrecommended: lower than default
Controls parallel job processing; lowering reduces memory spikes at cost of throughput
LANGFUSE_INGESTION_CLICKHOUSE_WRITE_BATCH_SIZErecommended: lower than default
Controls data batched per write; lowering reduces memory consumption
LANGFUSE_TOKEN_COUNT_WORKER_POOL_SIZErecommended: lower than 2 (default)
Tokenizer thread pool; high values cause pending requests to accumulate in memory
LANGFUSE_INGESTION_CLICKHOUSE_WRITE_INTERVAL_MSrecommended: 100
Flushes batches more frequently to prevent large payload buildup
Error Signatures (3)
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memoryexception
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memoryexception
Mark-Compactlog pattern
CLI Commands (2)
ps -eo pid,comm,args | awk "/[n]ode( |$)/ && !/node -e/ {print}"diagnostic
kill -USR1 $PIDdiagnostic
Technical References (10)
max-old-space-sizeconceptLangfuse Web containercomponentLangfuse Worker containercomponentBullMQcomponentNode.js heapconceptobservationsconceptingestion workerscomponentotel directoryfile path/api/public/ingestionendpointbatch processingconcept
Related Insights (6)
JavaScript heap out of memory error from insufficient Node.js memory allocationcritical
▸
Worker container high memory usage with low CPU under ingestion loadcritical
▸
Uneven memory distribution across worker replicaswarning
▸
Web container high memory usage with low CPU utilizationwarning
▸
High-cardinality traces (10K+ spans) cause Node.js heap exhaustion in ingestion workerscritical
▸
Ingestion endpoint requires more backend resources than other API endpointswarning
▸