Sphinx更新性能
Sphinx 2.0.1 带来了调用 UPDATE 并更新索引中单个项目的能力。
有谁知道当非常频繁地调用时（频率高达每秒数百次），这会给 sphinx 带来什么类型的性能？这样做的原因是保留趋势项目分数的实时索引，每次用户执行操作时该索引都会更新。显然，当有大量用户时，该值可以非常频繁地更新。
编辑：
我应该提到我没有使用SphinxSE。
Sphinx 2.0.1 brings with it the ability to call UPDATE and update an individual item in an index.
Does anyone know what type of performance this brings to sphinx when called VERY frequently (as frequently as several hundred times a second)? The reason for this would be to keep a real time index of trending item scores which get updated every time a user performs an action. Obviously when there are lots of users this value can be update quite frequently.
EDIT:
I should mention that I am not using SphinxSE.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您正在谈论 sphinx rt 索引...更新速度很快，但请记住，这种类型的索引不支持enable_star。这意味着您无法执行像
appl*这样的搜索。You are talking about sphinx rt indices... Updates are fast, but remember, this type of indices do not support enable_star. This means you can't perform searches like
appl*.这些属性存储在内存中。所以更新应该非常快。
但我从来没有对它进行过基准测试。所以尝试对它进行基准测试！
...尽管说实话，我仍然很想对其进行“批处理”。将操作写入日志“文件”，然后批量处理该日志。也许每 10 秒一次。同一记录上的所有操作都可以作为一个更新语句运行。
Such attributes are stored in memory. So updates should be really fast.
But I've never benchmarked it. So try benchmarking it!
... although to be honest I would still be tempted to 'batch process' it. Write the actions to a log "file", and then process that log in batches. Maybe every 10 seconds. All actions on the same record can be run as one update statement.