3 ms·

That’s a limitation you’ll hit pretty quickly unless you’ve specifically planned your architecture to be mostly read-only SQLite or one SQLite per session.

• spratzt 2y ago
  You certainly won’t hit it with most corporate OLAP processing, which is nearly all read-only SQlite. Writes are generally batched and processed outside ‘normal’ business hours, where the limitations of SQlite writing are irrelevant.
  • andai 2y ago
    Where are they batched?
    • chatmasta 2y ago
      In a separate system maintained by the DuckDB cargo cultists.
• conradev 2y ago
  I'm having a hard time imagining this. Aren't most CRUD apps using OLTP mostly read-only in the first place? I just feel like you'd need thousands of concurrent users on a typical CRUD app to even get close to straining SQLite.