Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

we only use a single thread with sqlite #8105

Open
richvdh opened this issue Aug 17, 2020 · 1 comment
Open

we only use a single thread with sqlite #8105

richvdh opened this issue Aug 17, 2020 · 1 comment
Labels
T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@richvdh
Copy link
Member

richvdh commented Aug 17, 2020

For reasons that are unclear to me, we only use a single thread with sqlite by default (see here).

I feel like this may be responsible for some of the poor performance seen with sqlite.

@clokep clokep added z-bug (Deprecated Label) z-p2 (Deprecated Label) labels Aug 17, 2020
@richvdh
Copy link
Member Author

richvdh commented Sep 10, 2021

One reason that we're only using a single thread might be to do with the blocking behaviour without Write-Ahead Logging enabled (according to #2917 (comment), "Non-WAL mode only supports either N concurrent readers or 1 writer, so writes can indefinitely block reads").

@erikjohnston erikjohnston added T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. and removed z-bug (Deprecated Label) z-p2 (Deprecated Label) labels Sep 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

3 participants