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
Significant JSON overhead compared to SQL #1794
Comments
Same in |
Interesting that if I disable auto-expansion, then in case of the
but So it looks like the issue has smth do with infix search. |
could be different default values for query via SQL and JSON endpoints |
Another example with a different keyword which makes the difference much bigger: 49 sec vs 671 ms
|
That is dupe of https://sphinxsearch.com/bugs/view.php?id=1253 |
I confirm it looks ok now:
@PavelShilin89 let's try to cover this with a small CLT test and see how stable it is in the github runners environment. Notes:
Result on dev2:
Please create a separate task for yourself about it and put a link here. |
In some case the same query which takes about 80ms via SQL can take 250ms via JSON.
MRE (dev2):
When there's only one disk chunk the difference is even larger (the likely related issue is #1767):
Version:
The text was updated successfully, but these errors were encountered: