I think the (unsatisfying) answer is "it depends". There's a huge amount of diversity in database workloads, even among the workloads served by SQLite as we mention in the paper. For read-mostly to read-only OLTP…
Thanks for the clarification. It's true that transaction latency is limited by the write speed of the storage medium. However, an "average desktop computer" these days has an SSD that can support tens of thousands of…
That's correct, the optimizations from this paper became available in SQLite version 3.38.0. As we were writing the paper, we did consider implementing hash joins in SQLite. However, we ultimately went with the Bloom…
I think the (unsatisfying) answer is "it depends". There's a huge amount of diversity in database workloads, even among the workloads served by SQLite as we mention in the paper. For read-mostly to read-only OLTP…
Thanks for the clarification. It's true that transaction latency is limited by the write speed of the storage medium. However, an "average desktop computer" these days has an SSD that can support tens of thousands of…
That's correct, the optimizations from this paper became available in SQLite version 3.38.0. As we were writing the paper, we did consider implementing hash joins in SQLite. However, we ultimately went with the Bloom…