Answer the question
In order to leave comments, you need to log in
Sphinx produces different results on the same configurations
Sphinx is behaving strangely. Very strange. On different machines, it produces different results for the same query with the same config and with the same indexed database. I love these kinds of problems.
What we have:
Two servers: FreeBSD virtualka and AMD64 Debian
The last Sphinx of the 2nd version, assembled directly from the trunk. Why from a trunk? Yes, it's just that stable searchd gives a segmentation error, a problem for a lot of people.
On FreeBSD, everything works fine - it finds everything you need, excellent relevance, and in fact it cannot be otherwise - the base is clear and simple. It turned out it could. On Debian, the result is that some of the information is not searched at all, the relevance does not work, although it finds something, it is clear that there are some matches.
At the same time, the configs are single (login/password/mysql_socket is different), everything is collected from one place, I even copied the sources from one server to another, and so I collected it. I tried to copy the index base - the result is zero.
On FreeBSD built:
./configure --prefix=/usr/local/sphinx --with-libstemmer --without-unixodbc (there were troubles)
On Debian built:
./configure --prefix=/usr/local/sphinx -- with-libstemmer
Bottom line: on the same copied index and config, the search command for the same word on different servers produces such different results that it becomes scary.
If everything is identical, what is left? Where to dig?
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question