solr 还是狮身人面像？哪个更好？
可能的重复：
选择独立全文搜索服务器：狮身人面像还是SOLR？
我将使用它在我的 ruby on Rails 应用程序中进行全文搜索。
这是最好的选择。
solr使用java来完成这项工作。或者红宝石中的狮身人面像？
Possible Duplicate:
Choosing a stand-alone full-text search server: Sphinx or SOLR?
I will use it to do full text search in my ruby on rails app.
which is the best choice.
solr use java to do this job. or sphix in ruby?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
我在不同的项目中使用了两者。我会继续使用 solr，因为它更容易安装：但这只是我的经验。您可以在此处获取更多信息。
I used both in different projects. I would stay with solr, as it was easier to install: but that is just my experience. You can get more information here.
我还尝试比较 Solr/Sphinx 并发现它们的另一种不同之处。它是搜索功能：
如果这些功能在您的开发环境中很重要，请查看 这个。
I'm also trying to compare Solr/Sphinx and found another way they are different in. It's search features:
If these features are important in context of your development, take a look at this.
我没有使用 Solr 的经验，但 Sphinx 易于安装、速度快，并且与 Thinking Sphinx 配合得很好： http://freelancing-god.github.com/ts/en/indexing.html
还有一个很好的railscast：
http://railscasts.com/episodes/120-thinking-sphinx
这家伙给你为什么选择 Sphinx 的一些争论：
http://jamesgolick.com/tags/ultrasphinx.html
（他使用 Ultrasphinx 插件来连接 Rails 和 Sphinx。我尝试了这两个插件，最终使用 Thinking Sphinx）
您可以在这里找到这两个插件的比较：
http://reinh.com/blog/2008/07 /14/a-thinking-mans-sphinx.html
I have no experience with Solr, but Sphinx is easy to install, fast and works great with Thinking Sphinx: http://freelancing-god.github.com/ts/en/indexing.html
There is also a good railscast:
http://railscasts.com/episodes/120-thinking-sphinx
This guy gives you some arguments why to go with Sphinx:
http://jamesgolick.com/tags/ultrasphinx.html
(He uses the Ultrasphinx plugin to connect Rails and Sphinx. I tried both and ended up using Thinking Sphinx)
You can find a comparison of both plugins here:
http://reinh.com/blog/2008/07/14/a-thinking-mans-sphinx.html
Solr 可以用 Java 实现，但这主要是一个实现细节。 Sphinx 基于 C++；你了解C++吗？ LucidImagination 提供了一个方便的 LucidWorks for Solr 发行版，可以为那些不熟悉的人进行部署Java 很快。
讽刺的是，Solr 比 Sphinx 具有更好的 Ruby 集成。有 acts_as_solr 可以插入 ActiveRecord，在纯 Ruby 级别也有一些不错的选择，但是那不是你的用例。您可能正在使用 Rails，但无论您选择的服务器端语言是什么，您可能需要考虑使用 AJAX-Solr 它有一个很棒的演示< /a>.最后，Solr 绝对是一个比 Sphinx 更大的项目，拥有更多的历史和信息来帮助您，包括 我的书。 LucidImagination 还提供免费的 PDF 参考指南。
Solr may be implemented in Java but that is mostly an implementation detail. Sphinx is C++ based; do you know C++? LucidImagination provides a convenient LucidWorks for Solr distribution that will make deployment for those unfamiliar with Java a snap.
Ironically, Solr has better Ruby integration than Sphinx. There's acts_as_solr which plugs into ActiveRecord, and at a pure ruby level there are a couple great options as well but that's not your use case. You may be using rails but no matter what your server side language of choice is, you might want to consider using AJAX-Solr and it's got a fantastic demo. Lastly, Solr is definitely a larger project than Sphinx with more history and information out there to help you including my book. LucidImagination offers a free PDF reference guide too.
虽然 sphinx 有 craigslist，但 Solr 有
http://www.lucidimagination.com/why-lucid/who-uses -lucene-solr
所以我认为答案很明确。
Although sphinx has craigslist, Solr has
http://www.lucidimagination.com/why-lucid/who-uses-lucene-solr
So I think the answer is quite clear.
我都尝试过，它们都很棒。就我而言，solr需要java（因为它基于lucene），而sphinx不需要。这就是为什么我选择 sphinx，除非我有充分的理由特别想要 solr。
I tried both, and they're both great. As far as I am concerned, solr requires java (since it's based on lucene), and sphinx doesn't. That's why I go with sphinx unless I have a very good reason to want solr specifically.
我的经验是针对小数据，认为 sphinx（或 ultra）对于那些只想让某些东西运行的开发人员来说是一个简单的搜索解决方案。一旦数据大于数据库中的十万行，那么两个插件都会暴露它们与活动记录的紧密耦合程度。然后，我们必须平衡 sphinx 索引何时执行（在 cron 中、在部署中等）、索引运行的频率、是否使用增量索引以及索引需要多长时间等之间的微妙关系。此外，一旦您的数据变得复杂（关于如何在搜索中显示结果以及显示什么结果），您就会开始觉得 sphinx 的可定制性受到限制。
我们正在将搜索从 sphinx 插件转移到独立于活动记录模型的开发和部署生命周期的东西。我们还没有决定是继续使用 sphinx 还是改用 solr。我们只是想让搜索和索引与模型分离，并将其拉出到我们的 Rails 应用程序所涉及的它自己的服务中。
My experience has been for small data, thinking sphinx (or ultra) have been an easy search solution to utilize for a developer just looking to get something running. Once the data is larger than say, one hundred thousand rows in the db, then both plugins expose how tightly coupled they are to active record. One then has to balance the delicate dance between when is the sphinx index executed (in cron, in deploy, etc.), how often indexing is run, is delta indexing used, and how much time indexing takes, among other things. Also, once your data gets complicated about how and what results should be exposed in search, you start to feel like the customizability of sphinx is limiting.
We are in the process of moving search out of a sphinx plugin into something independent of the development and deployment lifecycle of our active record models. We have not decided if we will continue to use sphinx or switch to solr. We just want to get search and indexing decoupled from the model and pulled out into it's own service that our rails application speaks to.