Menu

Sizing Langfuse Ingestion: ClickHouse Capacity, Redis Backpressure, and Span Economics
📰

Sizing Langfuse Ingestion: ClickHouse Capacity, Redis Backpressure, and Span Economics

DEV Community·Jangwook Kim·4 days ago
#qNnPxpCg
#dev#spans#langfuse#storage#article
Reading 0:00
15s threshold

Why We Brought This Tool Into Our Lab

We brought Langfuse into our evaluation because agent observability gets expensive in a way that request-based forecasts hide. One application request can generate a root span, several model calls, retrieval operations, tool executions, and retries. Multiply requests by observations per trace before buying infrastructure.

Published starting memory allocations Langfuse Web 4 GiB Langfuse Worker 4 GiB PostgreSQL 4 GiB Redis/Valkey 1.5 GiB ClickHouse 8 GiB

These are published starting allocations, not measured memory use or proof of ingestion capacity.

Our question was narrower than “Is Langfuse a good observability product?” We wanted to establish where ingestion accumulates, what competes with dashboard queries, and how to calculate cost per million spans without confusing accepted HTTP requests with queryable data.

Our local execution stopped before a benchmark: the required python:3.12-slim image was unavailable.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.