Comment Comment by vishnumohandas My bad, I linked to the wrong portion of the code. Here's the updated link[1].We are executing the entire write in a single batch query.From what we observed, and have documented, it is the serialization that is causing the bottleneck, not the write itself.Also, more than writes, it is the latency associated with deserializing the read data into models that pushed us to look at options outside SQLite.[1]: https://github.com/ente-io/edge-db-benchmarks/blob/43273607d... parent vishnumohandas 2 years ago
We are executing the entire write in a single batch query.
From what we observed, and have documented, it is the serialization that is causing the bottleneck, not the write itself.
Also, more than writes, it is the latency associated with deserializing the read data into models that pushed us to look at options outside SQLite.
[1]: https://github.com/ente-io/edge-db-benchmarks/blob/43273607d...