News for hackers. Stuff that matters.

A comment on SQLite: Past, Present, and Future. Parent comment

Re:SQLite: Past, Present, and Future by innocenat on Thursday September 01, 2022 @10:45AM (#32677025)
Where is write contention coming from if it's operated locally?
[ Parent | on HN ]
Re:SQLite: Past, Present, and Future by Thaxll on Thursday September 01, 2022 @10:51AM (#32677118)
SQLite is "single" threaded for writes.
[ Parent | on HN ]
Re:SQLite: Past, Present, and Future by d3nj4l on Thursday September 01, 2022 @11:00AM (#32677260)
... you can get tons of requests on a server?
[ Parent | on HN ]
Re:SQLite: Past, Present, and Future by dinosaurdynasty on Thursday September 01, 2022 @04:51PM (#32683007)
Redis has the same limitation (only one transaction at a time) and is used a lot for webapps. It solves this by requiring full transactions up front. The ideal case for sqlite for performance is to have only a single process/thread directly interacting with the database and having other process/threads send messages to and from the database process.
[ Parent | on HN ]
Re:SQLite: Past, Present, and Future by innocenat on Friday September 02, 2022 @09:58PM (#32697840)
But that isn't "locally"?
[ Parent | on HN ]