aboutsummaryrefslogtreecommitdiff
path: root/ext/wasm/api/sqlite3-vfs-opfs.c-pp.js
diff options
context:
space:
mode:
Diffstat (limited to 'ext/wasm/api/sqlite3-vfs-opfs.c-pp.js')
-rw-r--r--ext/wasm/api/sqlite3-vfs-opfs.c-pp.js10
1 files changed, 9 insertions, 1 deletions
diff --git a/ext/wasm/api/sqlite3-vfs-opfs.c-pp.js b/ext/wasm/api/sqlite3-vfs-opfs.c-pp.js
index 2e09aab21..13747ffec 100644
--- a/ext/wasm/api/sqlite3-vfs-opfs.c-pp.js
+++ b/ext/wasm/api/sqlite3-vfs-opfs.c-pp.js
@@ -1189,7 +1189,15 @@ const installOpfsVfs = function callee(options){
/* Truncate journal mode is faster than delete for
this vfs, per speedtest1. That gap seems to have closed with
Chrome version 108 or 109, but "persist" is very roughly 5-6%
- faster than truncate in initial tests. */
+ faster than truncate in initial tests.
+
+ For later analysis: Roy Hashimoto notes that TRUNCATE
+ and PERSIST modes may decrease OPFS concurrency because
+ multiple connections can open the journal file in those
+ modes:
+
+ https://github.com/rhashimoto/wa-sqlite/issues/68
+ */
"pragma journal_mode=persist;",
/*
This vfs benefits hugely from cache on moderate/large