5 ms·

I used it for ETL process extensive which is great. I still don't know how people use it for concurrent writes like a simple ToDo webapp?

• aidenn0 5y ago
  With WAL, writes for something like a ToDo app finish in a small fraction of a millisecond so unless your todo webapp is writing to the DB at a rate exceeding 20k writes per second, the fact that writes are not concurrent becomes largely irrelevant.
  • aynyc 5y ago
    This can't be right. As far as I can tell, WAL allows concurrent READS and WRITE, not concurrent WRITES. Am I doing this wrong all these years?
    • aidenn0 5y ago
      That's correct, it doesn't allow concurrent writes, but if the writes finish fast enough, that's somewhat academic.
      • aynyc 5y ago
        You still have to serialize the writes. If you have a lot of users on a simple ToDo apps, you can't do concurrent writes. I tried several times to run a simple webapp with Sqlite3 that have concurrent write requirement, the work around was too painful. I had to push all writes to an in-memory queue and have a single process pick off the queue. That process is outside of the web framework.
        • aidenn0 5y ago
          Why couldn't you do it in-process with a mutex? IIRC sqlite3 is thread-safe
          • aynyc 5y ago
            It's still a hassle, right? Especially in a WSGI environment for Python applications.