←back to thread

SQLite async connection pool for high-performance

(github.com)
197 points slaily | 1 comments | 11 Jul 25 10:26 UTC | HN request time: 0s | source
Show context
d1l ◴[14 Jul 25 21:08 UTC] No.44565326[source]▶
This is strange on so many levels.

SQLite does not even do network I/O.

How does sharing a connection (and transaction scope) in an asyncio environment even work? Won’t you still need a connection per asyncio context?

Does sqlite_open really take long compared to the inevitable contention for the write lock you’ll see when you have many concurrent contexts?

Does sqlite_open even register in comparison with the overhead of the python interpreter?

What is an asyncio SQLite connection anyways? Isn’t it just a regular one that gets hucked into a separate thread?

replies(4): >>44565652 #>>44568010 #>>44570930 #>>44572931 #
pjmlp ◴[15 Jul 25 13:28 UTC] No.44570930[source]▶
For some strange reason, some people feel like using SQLite all over the place, even when a proper RDMS would be the right answer.
replies(2): >>44571310 #>>44571407 #
fidotron ◴[15 Jul 25 14:05 UTC] No.44571310[source]▶
I recently encountered a shared SQLite db being used for inter process pub sub for real time data . . . in a safety critical system.

Wrong on so many levels it's frightening.

replies(2): >>44572901 #>>44577834 #
1. aynyc ◴[15 Jul 25 16:29 UTC] No.44572901[source]▶
Is it? It was designed for damage control system on naval combat vessels. I have no idea what it does on a naval vessel, but I imagine there is certain level of safeness.