5 comments

  • tptacek 22 minutes ago
    "Idle cost is that one lightweight SELECT per millisecond per database — no page-cache pressure, no writer-lock contention, no kernel file watcher in the mix."

    I think (respectfully) the LLM that probably wrote this overshot the mark here because busy-polling a select does not actually sound better to me than a "kernel file watcher".

    • felooboolooomba 3 minutes ago
      "one lightweight SELECT per millisecond"

      This reminds me of the teenager who told her dad that she was just a tiny little bit pregnant.

  • vmsp 20 minutes ago
    Reminds me of Litestack for Rails. Eventually, it was abandoned because Rails itself started going all out on SQLite.

    https://github.com/oldmoe/litestack

  • itopaloglu83 1 hour ago
    It’s an interesting approach and can be quite fun to use for new projects.

    > How it works: honker polls SQLite’s PRAGMA data_version every millisecond. That’s a monotonic counter SQLite increments on every commit from any connection, journal mode, or process — a ~3 µs read for a precise wake signal.

  • EvanAnderson 1 hour ago
    Prior discussion a few days ago: https://news.ycombinator.com/item?id=47874647
  • arlobish 32 minutes ago
    At the end it says: "pg-boss and Oban are the Postgres-side gold standards" -- but Oban supports SQLite now too https://github.com/oban-bg/oban