perf: add an opt-in read-only connection pool
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 28/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- android, ios, react-native, sqlite
- 领域
- database, mobile, performance
调研方向
Start by reviewing the existing independent read-only connection API and native FIFO behavior, then compare one connection with a small read pool on mixed read/write workloads for queue wait, query time, memory, WAL size, and battery/CPU cost on iOS and Android. Done requires recorded measurements before implementation, plus documented journal-mode and snapshot semantics and a clearly scoped opt-in pool lifecycle.
由索引模型根据 Issue 内容生成。
描述
NitroSQLite now supports independent read-only connections to one database file, but callers must create, select, and close each connection themselves. A write-heavy app with long reads may benefit from an opt-in pool that routes independent read queries across a bounded set of handles while retaining one writer connection.
Design a small pool API on top of the existing independent-connection and native FIFO behavior. Bound the connection count, preserve each connection's configuration, reject writes on reader handles, and close all handles only after outstanding work has settled or been cancelled. Document the SQLite journal mode and snapshot semantics; a pool must not silently change a database's journal mode or promise parallel writes.
Before implementation, compare one connection with a small read pool on realistic mixed read/write workloads. Record queue wait, query time, peak memory, WAL size, and battery/CPU cost on iOS and Android. Avoid a default pool until measurements show a benefit beyond the existing independent-connection API.
Related: #62, #364, #369. The independent read-only connections are already available; this issue tracks automatic routing and lifecycle only.
- 主要语言
- C
- 星标
- 579
- 派生
- 53
- 平均合并
- 2 天 5 小时
- 30 天内合并 PR
- 67
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
margelo/react-native-nitro-sqlite 的其他 Issue
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 35/100
margelo/react-native-nitro-sqlite#402 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 35/100
margelo/react-native-nitro-sqlite#400 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 28/100
margelo/react-native-nitro-sqlite#399 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 35/100
margelo/react-native-nitro-sqlite#398 ·
维护者通常 1 天内回复
-
area:api area:runtime enhancement
难度 5/5 一周以上 新手友好度 48/100
margelo/react-native-nitro-sqlite#397 ·
维护者通常 1 天内回复
查看 margelo/react-native-nitro-sqlite 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
dkfans/keeperfx#5415 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
ARM-software/sysarch-acs#600 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 74/100
EchoTools/nevr-runtime#117 · 2 条评论 ·
维护者通常 1 天内回复