Plone CMS：与典型 CMS GET 请求相比，搜索请求有多重？
Plone CMS：与典型 CMS GET 请求相比，搜索请求有多重？
我担心在大型站点（50 万个文档）上启用搜索功能需要 DOS。如果是这样，如何减轻这种威胁？搜索可以在不同的 ZOE 实例上运行吗？
Plone CMS: how heavy are search requests compared to typical CMS GET requests?
I fear that on a large site (0.5 milions of documents) enabling search capability is asking for DOS. If so, how this threat can be mitigated? Can search work on a different ZOE instance?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Plone的portal_catalog相当高效/快速/优化。它不像 SQL 查询，您可以在其中构建需要几分钟才能完成的搜索。
最重要的部分通常是在呈现搜索结果时“唤醒”对象，您应该尽可能地使用目录返回的元数据（所谓的“大脑”）。无论如何，这就是 Plon 默认尝试做的事情。
但是，如果您认为这可能是瓶颈，您仍然可以使用单独的 ZEO 实例来处理搜索请求。只需确保对 /search 和 /search_form（或一般而言，/search*）的请求最终到达此特定的 ZEO 实例。如何执行此操作取决于当前的负载平衡设置（apache、squid、nginx 等）
Plone's portal_catalog is rather efficient/fast/optimized. It's not like an SQL Query where you can construct searches that take minutes to complete.
The heavy part is usually "waking up" objects when presenting the search results, you should work as much as possible with the metadata (so called "brains") that the catalog returns. This is what Plone tries to do by default anyway.
But still, you can use a seperate ZEO instance for handling search request if you feel that this may be a bottleneck. Just make sure requests for /search and /search_form (or generically, /search*) end up at this specific ZEO instance. How you do this is rather specific to your current load balancing setup (apache, squid, nginx, etc)
有了这么多文档，您想要研究一个专用的搜索系统 - Plone 的文本索引确实不是那么好。查看 http://plone.org/products/collective.solr 了解 Plone 集成与 http://lucene.apache.org/solr/ 或 http://pypi.python.org/pypi/collective.gsa（如果您有 Google Search Appliance）。
With that many documents you want to be investigating a dedicated search system - Plone's text indexes are really not that great. Take a look at http://plone.org/products/collective.solr for a Plone integration with http://lucene.apache.org/solr/ or http://pypi.python.org/pypi/collective.gsa if you have a Google Search Appliance.
Plone 的搜索引擎非常棒，因为它完全集成并且默认安装。当您的网站增长到包含 50 万个文档的区域时，您通常需要更可靠的搜索。
我们在大型项目中使用 SOLR 并取得了巨大成功，并且已经存在与 Plone 的多个集成：
http://plone .org/products/collective.solr
http://plone.org/products/alm.solrindex
http://plone.org/products/collective.recipe.solrinstance
Plone's search engine is awesome in that it is fully integrated and ships with the default install. When your site grows to areas of 500k documents you generally want a more solid search.
We have used SOLR with great success is large projects, and there already exist several integrations with Plone:
http://plone.org/products/collective.solr
http://plone.org/products/alm.solrindex
http://plone.org/products/collective.recipe.solrinstance