If you use the Sphinx search engine and have been watching the development branch (0.9.10) and wondering when to upgrade, I'm here to tell you that "now" is a great time. As of r2037, the last major issue I regularly saw has been fixed. The other big bug was fixed in r2031.
Late last week I began testing those fixes in a "burn-in" test I've developed that makes liberal use of
indextool --check. Instead of seeing index corruption within an hour, I saw none. After 3 days of no failures, I deployed it to a subset of our search back-end servers. Yesterday we deployed it to half of the remaining servers.
So far, so good!
I should note that all our index corruption was merge related. Sphinx wasn't building corrupt indexes out of the box, but the merges (usually filtering merges) could produce corrupted indexes.
We were upgrading from a lightly patched version of r1894. That meant rebuilding our indexes to use the new and more compact format. Some of the obvious benefits of the upgrade:
- smaller disk and memory footprint
- pre-fork support to spawn searchd children at start up
- more reliable shutdown and pid file handling
- kill lists
- mysql protocol support
- lots of small optimizations and fixes
Thanks to the Sphinx team for their excellent work. I look forward to the release of Sphinx 1.0.
Posted by jzawodn at October 30, 2009 07:26 AM
Thanks for your update. I wrote a review of the previous release and was worried when I read about some of the bugs on this one.
I can't wait to test 1.0 either.
I've never heard Sphinx search engine before. I'm gonna try this now. Thanks for sharing this
I am also using the net since 10 years and Sphinx search is new to me i found about it through your post only.
I 've heard about Sphinx before. But never used it thinking that its not necessary or worth. Reading your article ( this one and your previous one ) I think it can do something with business. Let me give it a try. Thanks for sharing it.
PS: If your blog is having a quick - easy subscription button that will be great.
I've have to check this out. Thanks.
Thanks for your post i would like to have regular visit to it
We've been having a lot of sphinx performance issues in sphinx 0.99-rc1. I think searchd's forking is a big reason why. I am going to give the latest a try and see what happens.
Is there somewhere a document outlining how forking works? What the searchd child does on startup, when it starts up, how long it lives ... ?
Sphinx like other search engines is overshadowed by the great Google.
But I think that people should go use other search engines too. If their usage increases then the one sided equation of Google could change and needless to mention there is a vast possibility of huge knowledge data banks
Fantastic website I will bookmark it and come back later.
Thanks for posting this. Very nice recap of some of the key points in my talk. I hope you and your readers find it useful! Thanks again