虚拟Actor状态查询与写入性能痛点
问题概述
用户在使用虚拟Actor模型时，需要维护多个数据库以便查询状态，导致状态冗余和Schema变更风险；同时，写入延迟约为100ms，对实时应用不友好，与Celld等方案的1ms写入形成鲜明对比。
痛点标签
- 虚拟Actor状态查询需要额外数据库冗余，且易受Schema变更影响
- 写入延迟约100ms，不适合实时应用
待验证问题
- 您是否在实际项目中遇到过虚拟Actor状态查询的冗余问题？
- 您对写入延迟的容忍度是多少？
证据
原话
Looks great but one of the common problems with the virtual actor model is state query. It's all well and good to have nice separated state dbs but for most use cases that means further double up on storing the state again in another database that can query it. I don't think anyone has come up with a nice solution for this problem without using a loose document database, but even then actors can change their schema.
原话
100ms for a write - not usable for anything beyond toys. I mean we have https://github.com/denoland/celld - with a known good open source history. Durable writes there are as low as 1ms.
免责声明：本卡片由 AI 从社区讨论中提炼，属于「痛点证据」，是需求分析与验证的起点，不等同于「已验证的市场需求」。AI 存在分析局限，关键决策前请打开上方原始讨论人工复核。