Performance degradation in response time using range filters from Qdrant version 1.6 onwards about qdrant HOT 4 OPEN

Hey @marevol, in the context of ANN search, measuring latency without accuracy might be misleading.
Could you please confirm that those measurements you provide also yield same level of accuracy?

from qdrant.

Thank you for raising this point.
Our tests are designed to focus on latency, not accuracy, and use consistent conditions across different versions.
Given the significant impact on latency that we've observed, were there any major changes made to improve accuracy starting from version 1.6, which might explain this increase in latency?
For accuracy, I will check this aspect later.

from qdrant.

Given the significant impact on latency that we've observed, were there any major changes made to improve accuracy starting from version 1.6, which might explain this increase in latency?

there were some

from qdrant.

I have checked the precision@100 for accuracy across the versions.

• Version 1.4.1: Precision@100 = 0.9310
• Version 1.5.1: Precision@100 = 0.9293
• Version 1.6.1: Precision@100 = 0.9271
• Version 1.7.4: Precision@100 = 0.9396
• Version 1.8.4: Precision@100 = 0.9354

It appears that there are no significant differences in accuracy between the versions.

from qdrant.