3 ms·
I can sympathize! I'm using an encrypted database on the device and there are some real slowdowns. For as far as I trace the code, the only part I can't really
by alexc05 11y ago
I can sympathize! I'm using an encrypted database on the device and there are some real slowdowns.
For as far as I trace the code, the only part I can't really optimize is the db open commands
For the most part it's pretty slick, but I can still feel it. It could be faster.
- MichaelApproved 11y agoOne database trick I used was to pre-select queries in the background and cache the results. It creates some code overhead for updating/inserting that has to keep the cache in sync. However, it simplified the logic in the rest of the code because I didn't need a promise for a select, I just read the cached object. That allows me to outsource the controllers for screens to developers who don't have to work with promise overload. They access my wrapper service for the content using synchronized code. My database is also very simple. If you have a complicated schema with lots of joins, it'll be tough to cache things and keep it in sync with the db. Feel free to email me, if you want more details on this concept.