Configuration on Qdrant - Vector Search Engine

Configuration

info@qdrant.tech (Andrey Vasnetsov) — Mon, 01 Jan 0001 00:00:00 +0000

Configuration

Qdrant ships with sensible defaults for collection and network settings that are suitable for most use cases. You can view these defaults in the Qdrant source. If you need to customize the settings, you can do so using configuration files and environment variables.

Configuration Files

To customize Qdrant, you can mount your configuration file in any of the following locations. This guide uses .yaml files, but Qdrant also supports other formats such as .toml, .json, and .ini.

Administration

info@qdrant.tech (Andrey Vasnetsov) — Mon, 01 Jan 0001 00:00:00 +0000

Administration

Qdrant exposes administration tools which enable to modify at runtime the behavior of a qdrant instance without changing its configuration manually.

Recovery mode

Available as of v1.2.0

Recovery mode can help in situations where Qdrant fails to start repeatedly. When starting in recovery mode, Qdrant only loads collection metadata to prevent going out of memory. This allows you to resolve out of memory situations, for example, by deleting a collection. After resolving Qdrant can be restarted normally to continue operation.

Usage Statistics

info@qdrant.tech (Andrey Vasnetsov) — Mon, 01 Jan 0001 00:00:00 +0000

Usage statistics

The Qdrant open-source container image collects anonymized usage statistics from users in order to improve the engine by default. You can deactivate at any time, and any data that has already been collected can be deleted on request.

Deactivating this will not affect your ability to monitor the Qdrant database yourself by accessing the /metrics or /telemetry endpoints of your database. It will just stop sending independent, anonymized usage statistics to the Qdrant team.

Running with GPU

info@qdrant.tech (Andrey Vasnetsov) — Mon, 01 Jan 0001 00:00:00 +0000

Running Qdrant with GPU Support

Starting from version v1.13.0, Qdrant offers support for GPU acceleration.

However, GPU support is not included in the default Qdrant binary due to additional dependencies and libraries. Instead, you will need to use dedicated Docker images with GPU support (NVIDIA, AMD).

Configuration

Qdrant includes a number of configuration options to control GPU usage. The following options are available:

gpu:
 # Enable GPU indexing.
 indexing: false
 # Force half precision for `f32` values while indexing.
 # `f16` conversion will take place 
 # only inside GPU memory and won't affect storage type.
 force_half_precision: false
 # Used vulkan "groups" of GPU. 
 # In other words, how many parallel points can be indexed by GPU.
 # Optimal value might depend on the GPU model.
 # Proportional, but doesn't necessary equal
 # to the physical number of warps.
 # Do not change this value unless you know what you are doing.
 # Default: 512
 groups_count: 512
 # Filter for GPU devices by hardware name. Case insensitive.
 # Comma-separated list of substrings to match 
 # against the gpu device name.
 # Example: "nvidia"
 # Default: "" - all devices are accepted.
 device_filter: ""
 # List of explicit GPU devices to use.
 # If host has multiple GPUs, this option allows to select specific devices
 # by their index in the list of found devices.
 # If `device_filter` is set, indexes are applied after filtering.
 # By default, all devices are accepted.
 devices: null
 # How many parallel indexing processes are allowed to run.
 # Default: 1
 parallel_indexes: 1
 # Allow to use integrated GPUs.
 # Default: false
 allow_integrated: false
 # Allow to use emulated GPUs like LLVMpipe. Useful for CI.
 # Default: false
 allow_emulated: false

It is not recommended to change these options unless you are familiar with the Qdrant internals and the Vulkan API.