Replies: 1 comment 2 replies
-
|
Did you find an answer? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for asking. Are you able to reöpen the discussion? Because, no, I did not find an answer. If it helps, it's running on a windows server. With the database open in "DB Browser for SQLite", the entire request takes ~200ms. When the database is not open in "DB Browser for SQLite", the router.get function, which has the database access, takes about 1.2 seconds. And then expressjs logs ~6 seconds to complete the request. Also, I think strangely, the behaviour is the same both when "DB Browser for SQLite" has opened the db file normally and the file is opened in read only mode. |
Beta Was this translation helpful? Give feedback.
-
|
actually, I've disabled WAL and it works properly now. I think there wasn't permission to write to the wal file, and so there was a 5 second delay each time while that timed out. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm running expressjs v4, better-sqlite3 v7. My web app is very slow. Routine select queries take about 6-7 seconds. This is with or without the WAL journal mode. BUT when I have "DB Browser for SQLite" open on the server, with the database file open in it, suddenly queries are only around 300-500 milliseconds! — which is the behaviour I want and expect. Does anyone have any idea why this might be? What does sqlite browser do when opening the file, that might not being done when used via expressjs/better-sqlite3 ? If I understood that, I might be able to set it up so that the delay does not occur.
Beta Was this translation helpful? Give feedback.
All reactions