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 摘要。