Measure search latency under sustained writes and revisit the read-after-write default

未关闭
#4 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
39/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript

调研方向

Read DESIGN.md, especially “Searchable at commit,” and inspect the search paths that pass waitForIndexMilliseconds. Measure search latency during a realistic sustained write rate, then use the results to decide whether read-after-write remains the default or becomes opt-in. Done means the measurements and a decision are documented.

由索引模型根据 Issue 内容生成。

描述

Problem

Both search lanes pass waitForIndexMilliseconds so that a memory is searchable as soon as its write commits (DESIGN.md "Searchable at commit"). The cost was measured once on a single local node (Harper 5.3.2): 6–13 ms with no recent write, about 1 s for a search right after any write, and no delay from another write's open transaction. Under a steady write rate, most searches would pay the ~1 s.

Proposed

Measure search latency under a realistic sustained write rate and decide whether read-after-write should stay the default or become opt-in (e.g. fresh=true, or only for the caller's own recent writes).

Review-Deferral: 55ad204238431ba4 severity=minor category=performance

🤖 Generated by Claude Opus 5.5 (Claude Code); posted via @kriszyp.

主要语言
JavaScript
星标
0
派生
0
平均合并
20 小时 29 分钟
30 天内合并 PR
28

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

HarperFast/agent-memory 的其他 Issue

查看 HarperFast/agent-memory 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。