-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance degradation in response time using range filters from Qdrant version 1.6 onwards #4071
Comments
Hey @marevol, in the context of ANN search, measuring latency without accuracy might be misleading. |
Thank you for raising this point. |
there were some |
I have checked the precision@100 for accuracy across the versions.
It appears that there are no significant differences in accuracy between the versions. |
Current Behavior
Since upgrading to the latest version of Qdrant, we have noticed that the response times have increased when using range filters during vector searches. To confirm this problem, I prepared test code. In these experiments, response times were about 1 millisecond in version 1.5 and earlier; however, from version 1.6 onwards, the response time has increased to about 3 milliseconds.
Steps to Reproduce
To reproduce this issue, we created a test code in the codelibs/search-ann-benchmark repository, which can be found here. This test involves the following steps:
In version 1.8.4, changing the field schema to integer with settings of lookup:false & range:true showed some improvement:
Although this setting shows an improvement, the response time is still slower compared to earlier versions.
Expected Behavior
We expect the response times using range filters in vector searches to be similar to those in previous versions.
Context (Environment)
The environment used for testing includes:
The text was updated successfully, but these errors were encountered: