3 ms·
What people are saying is your premise is wrong, and you’re getting defensive. Either of those would not be an interesting problem except that your title is ca
by hinkley 3y ago
What people are saying is your premise is wrong, and you’re getting defensive.
Either of those would not be an interesting problem except that your title is calling out a particular and beloved database as being the culprit. Which feels a lot like defamation.
Even if deserialization is the bottleneck, bottlenecks are relative and don’t have to be singular. You can have multiple bottlenecks and being blind to one because of PEBCAK can still skew results and thus conclusions.
The people you’re responding to want you to fix your code and run it again. I think that’s reasonable. And maybe deserves a follow up post or a rework of the existing one.
- vishnumohandas 3y agoSorry if I sounded defensive! I have nothing against SQLite, but I unfortunately haven't yet understood how to write and read Lists more efficiently. Once I do, I'll definitely post a follow up :)
- vishnumohandas 3y agoUpdate: https://ente.io/blog/tech/sqlite-objectbox-isar#update https://ente.io/blog/tech/sqlite-objectbox-isar#update TL;DR: Removing Protobuf and directly serializing the list to a blob helped!