Persistence and memory
Qdrant uses persistent storage for its database data under the configured storage directory, while indexes and working data also consume memory during operation. The exact memory footprint depends on the collection, index configuration, payload indexes, caching, and workload.
For containers, the important operational point is that the storage directory must live on durable storage if data must survive container replacement. A container's writable layer is not a reliable database persistence strategy.
Memory sizing also matters because vector indexes can consume substantial RAM. Persisting data to disk does not mean the database can operate with arbitrarily little memory; search performance and index behavior still depend on available resources.
A common mistake is thinking 'the database is on disk, therefore RAM does not matter.' Production sizing must account for both persistent storage and memory used by indexes and active workloads. Exact storage and memory behavior can vary by Qdrant version and configuration.
Mount durable storage at Qdrant's storage directory
Container filesystem layers should not be treated as durable database storage
Vector and payload indexes can require substantial memory
Size disk and RAM independently according to workload and configuration
0-2 years experience
2-5 years experience
5-8 years experience
8+ years experience
