Top all-time · #7999
Oldmoe's blog
Personal blog · oldmoe.blogprogrammingsystems
Oldmoe's blog is a personal blog at oldmoe.blog about programming and systems. Since 2024, 10 different Hacker News readers have linked it 14 times, most often “Smaller, faster serialization for Ruby apps and beyond”. It is still writing: the last post was on 2026-10-02, and you can follow it by feed.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for its SQLite write-performance material. One commenter cites its post on scaling SQLite writes beyond WAL and Begin Concurrent limits with synchronous writes. Another discusses Django SQLite production PRAGMAs.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Musings about life, technology and some unrelated stuff
Most-linked posts?
- Smaller, faster serialization for Ruby apps and beyond3 people · 4 mentions · first linked 2025-05-05
- Backup Strategies for SQLite in Production3 people · 3 mentions · first linked 2024-04-30
- The Write Stuff: Concurrent Write Transactions in SQLite3 people · 3 mentions · first linked 2024-07-18
- Turn on MMAP support for your SQLite connections2 people · 2 mentions · first linked 2024-06-15
- LiteCluster: Replicated, Leaderless, Consistent SQLite2 people · 2 mentions · first linked 2024-07-23
What Hacker News says?
You can make SQLite scale way beyond the limitations of WAL mode or even Begin Concurrent mode, all while doing synchronous writes https://oldmoe.blog/2024/07/08/the-write-stuff-concurrent-wr...
Comment linking /2024/07/08/the-write-stuff-concurrent-write-transactions-in-sqlite/
on “Show HN: SQLite Transaction Benchmarking Tool”Submitted Backup Strategies for SQLite in Production as a story · 37 points
HN discussionI did the exact same thing yesterday, couple of notes: If you subclass sqlite3.base.DatabaseWrapper, it will issue the required PRAGMAs defined by Django, where foreign_keys = ON and legacy_alter_table = OFF. I don't think synchronous = NORMAL worth it, as there is a tiny-tiny chance you will lose data. The relevant section from SQLite doc: "A transaction committed in WAL mode with synchronous=NORMAL might roll back…
Comment linking /2024/02/03/turn-on-mmap-support-for-your-sqlite-connections/
on “Django SQLite Production Config”Submitted Backup Strategies for SQLite in Production as a story · 5 points
HN discussionSubmitted The Write Stuff: Concurrent Write Transactions in SQLite as a story · 4 points
HN discussionSubmitted Smaller, faster serialization for Ruby apps and beyond as a story · 4 points
HN discussionSubmitted Backup Strategies for SQLite in Production as a story · 4 points
HN discussionSubmitted TinyBits: Smaller, faster serialization for Ruby apps and beyond as a story · 3 points
HN discussionSubmitted Smaller, faster serialization for Ruby apps and beyond as a story · 3 points
HN discussionSubmitted Smaller, faster serialization for Ruby apps and beyond as a story · 3 points
HN discussionSubmitted Turn on MMAP support for your SQLite connections as a story · 2 points
HN discussionSubmitted LiteCluster: Replicated, Leaderless, Consistent SQLite as a story · 2 points
HN discussionSubmitted The Write Stuff: Concurrent Write Transactions in SQLite (2024) as a story · 1 points
HN discussionSubmitted LiteCluster: Replicated, leaderless, ACID compliant and high availability SQLite as a story · 1 points
HN discussion
