After the upgrade from 4.9.0 to 4.16.0, the query time is longer

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
android, c

调研方向

No source file or test is named. Start by reproducing the Android scenario with WAL enabled and many SQL queries, then compare versions 4.13.0 and 4.14.0 while varying KDF_inter; done means identifying the regression and providing a verified performance improvement without disabling WAL.

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

描述

According to my testing, version 4.13.0 is okay, but it starts to deteriorate from version 4.14.0 onwards.

Scenario: I am running the environment in an Android app with WAL enabled. When the app is opened for the first time, the query performance deteriorates, but after some time, the query performance returns to normal.

My speculation: Version 4.13.0 replaced the default encryption component, which significantly increased the computational time for each key derivation function (KDF) operation.

My tests:
Test 1: Disabling WAL improved the query performance significantly.
Test 2: Setting KDF_inter = 64000 improved the query performance significantly.

In version 4.9.0, when the app is opened for the first time, under a large number of SQL queries, the longest read time is <500ms.
In version 4.14.0, when the app is opened for the first time, under a large number of SQL queries, the longest read time is 3s to 7s.

主要语言
C
星标
7.3k
派生
1.4k
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

sqlcipher/sqlcipher 的其他 Issue

查看 sqlcipher/sqlcipher 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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