Performance Tuning
Starting in 0.3.9, Epsilla Vector Database offers advanced performance tuning options to cater to diverse operational needs, ensuring optimal efficiency and speed for vector data processing. By adjusting the configuration through a simple POST request to the API endpoint, users can fine-tune the database's performance to their specific requirements:
Note: all the config entries are optional. If not provided, the entry value will stay as default (shown in the table below).
Here's a table that succinctly presents the performance tuning parameters supported by Epsilla Vector Database:
IntraQueryThreads
4
Controls the number of threads used within a single query, enabling efficient parallel processing for a single vector search query. Set a larger value to get a lower query latency. Note: increasing the value will reduce the throughput the whole system can handle.
ConcurrentWorkersPerIndex
16
Sets the number of concurrent workers. Enables concurrent query processing. Set to a larger value to get better throughput. Note: IntraQueryThreads * ConcurrentWorkersPerIndex
should not exceed Total available threads - RebuildThreads
, otherwise the increased context switch will reduce the overall system performance.
RebuildThreads
1
Determines the number of threads allocated for rebuilding vector indexes. Set to a larger value to get a faster indexing rebuild.
SearchQueueSize
500
Adjusts the size of the search queue. The larger the value, the higher the recall of vector search (especially in metadata filtering), with a tradeoff of higher query latency.
Last updated