diff options
| author | stephan <stephan@noemail.net> | 2022-11-10 11:35:10 +0000 |
|---|---|---|
| committer | stephan <stephan@noemail.net> | 2022-11-10 11:35:10 +0000 |
| commit | aafa022f5b5371d83ee3478c17e0c7f2faf1ce62 (patch) | |
| tree | ee1cfed1ad1cd869c8d5561f4a92e3df68521456 /ext/wasm/api/sqlite3-api-opfs.js | |
| parent | 838865c0bb3531a4105567dfc1f6623c6aa1cd5f (diff) | |
| download | sqlite-aafa022f5b5371d83ee3478c17e0c7f2faf1ce62.tar.gz sqlite-aafa022f5b5371d83ee3478c17e0c7f2faf1ce62.zip | |
OPFS: if an op which needs a lock is called when no lock has been obtained, automatically lock it at the start of the op and unlock it at the end of that op. This is an attempt to alleviate the cross-tab contention described in [forum post 58a377083cd24a|forum:58a377083cd24a] but it increases speedtest1 run time by approximately 4x. Perhaps auto-lock can be combined with the older idle-time-based auto-unlock to unlock such locks (but not those from xLock()) to improve this?
FossilOrigin-Name: 46304ba057707c3b072b6e7bb8c4af774f653aa5814099f0866cd87b2b73abeb
Diffstat (limited to 'ext/wasm/api/sqlite3-api-opfs.js')
0 files changed, 0 insertions, 0 deletions