QuestDB · Rate Limits

Questdb Rate Limits

QuestDB does not enforce a managed-service-style request quota. As a self-hosted database, the relevant limits are operational: max concurrent HTTP/PG connections, ILP TCP buffer/queue depth, query timeouts, and per-server CPU/IO budgets. Limits are configurable via server.conf.

4 Limits
DatabaseTime-SeriesSQLOpen SourcePerformanceRate LimitingQuotasThrottling

Limits

HTTP REST default workers server
workers
see http.worker.count in server.conf
Default tuned to host CPU; controls request concurrency on port 9000.
Postgres wire connections server
connections
see pg.net.connection.limit in server.conf
Default 64 connections on port 8812.
ILP TCP connections server
connections
see line.tcp.net.connection.limit in server.conf
Default 256 ILP TCP connections on port 9009.
Query timeout server
ms
see query.timeout.sec in server.conf
Long-running queries are terminated server-side.

Policies

Backoff Strategy
ILP HTTP clients should retry on 5xx with exponential backoff; ILP TCP clients should buffer and reconnect on disconnect.
Capacity Planning
Size workers, RAM and disks per QuestDB capacity-planning guide; no managed throttling.

Sources