lucene php mysql_php mysql全文搜索:lucene, sphinx還是?

This is admittedly similar to (but not a duplicate of) Comparison of full text search engine - Lucene, Sphinx, Postgresql, MySQL?, however what I am looking for are specific, supported, recommendations from the benefit of experience with more than one of the available systems (there seems to be a lot of: "I've used lucene, but not sphinx", and vice a versa).

這與全文搜索引擎(Lucene, Sphinx, Postgresql, MySQL?)的比較類似(但不是重復)。然而，我正在尋找的是具體的、受支持的建議，這些建議來自於使用不止一個可用系統的經驗(似乎有很多:“我使用過lucene，但沒有sphinx”，反之亦然)。

The setup: Standard LAMP (Mysql 5.0, PHP 5).

設置:標准LAMP (Mysql 5.0, PHP 5)。

MySQL: tables are using the InnoDB engine for foreign key constraints

MySQL:表使用InnoDB引擎進行外鍵約束

We are looking at indexing data, not pages. data to be indexed may be in multiple languages (utf-8 charset)

我們關注的是索引數據，而不是頁面。要索引的數據可以使用多種語言(utf-8字符集)

A number of the comparisons I've come across (like http://blog.evanweaver.com/articles/2008/03/17/rails-search-benchmarks/) are either not entirely applicable (ferret is a lucene port but not the same as Zend_Search_Lucene) or they are pushing their own systems/implementations (not exactly unbiased).

我遇到的許多比較(比如http://blog.evanweaver.com/articles/2008/03/17/rails-search-benchmarks/)不是完全適用的(ferret是lucene端口，但不等同於Zend_Search_Lucene)，或者他們正在推廣自己的系統/實現(並非完全沒有偏見)。

我遇到的其他一些人(比如http://whattheplot.com/blog/tag/lucene/和http://pagetracer.com/2008/02/15/sphinx- lucene-search- enges -first- sions/)為這兩種系統的性能提供了非常不同的結果。

Also, all but ignored in much of what I've read is Xapian. Might this be worth consideration as well?

而且，在我讀到的很多文章中，幾乎都忽略了Xapian。這也值得考慮嗎?

So... I'm hoping that some of you here on SO have some experience with this question and could help with some recommendations or point me in the right direction.

所以…我希望在座的一些人對這個問題有一些經驗，能給我一些建議，或者給我指出正確的方向。

2 个解决方案

#1

9

One advantage of Sphinx is that you can "interpose" it between your clients and the MySQL server, and it will only "interfere" on queries specifically addressing it, transparently bouncing the others off MySQL -- see e.g this article. Whether that's an advantage in your use case, you're best placed to say!

Sphinx的一個優點是，您可以在客戶端和MySQL服務器之間“插入”它，而且它只會“干擾”特定的查詢，透明地將其他用戶從MySQL中彈出——參見e。本文g。無論這在您的用例中是否是一個優勢，您都是最好的人選!

Sorry, no real-life experience with Xapian or Lucene -- still, reading about how to deploy them, makes it sound like (to me!) as if it might be worth it only if you identified substantial advantages. Otherwise, Sphinx's "easy as pie" deployment, as a "proxy" between your clients and your MySQL server, feels like a big, substantial win to me!

對不起，沒有Xapian或Lucene的實際經驗——不過，閱讀有關如何部署它們的文章，會讓人覺得(對我來說!)似乎只有在你發現了實質性的優勢之后，才值得這么做。否則，Sphinx作為客戶端和MySQL服務器之間的“代理”的“簡單如餅”部署，對我來說是一個巨大的、實質性的勝利!

#2

3

I looked at Zend_Search_Lucene and Sphinx for a project that sounds similar - searching database content (in my case, book information). I spent about a day looking at each. For what it's worth, I found Sphinx vastly easier to set up and use.

我查看了Zend_Search_Lucene和Sphinx，找到了一個聽起來很相似的項目——搜索數據庫內容(在我的例子中是圖書信息)。我花了大約一天的時間觀察每一個。對於它的價值，我發現Sphinx非常容易設置和使用。