Hello!
We are in the process of trying to squeeze the performance of our app start. SQLite it's a hard dependency when starting so we are currently waiting for the sqlite_async (Powersync) factory to initialize before showing the interactive UI to the users. At the moment we are comfortable with 5 readers, but that means that on app start we need to wait for the initialization of all the readers in the pool (about 1.3 s on my emulator). If we use 1 reader, time is reduced to 500 ms.
What we were thinking is if there could be a way to open with 1 writer / 1 writer + 1 reader, and then have some way of adding more readers at runtime.
We would open the app as thin as possible and then asynchronously spawn the other readers when the user can interact with the UI.
Thanks!
Hello!
We are in the process of trying to squeeze the performance of our app start. SQLite it's a hard dependency when starting so we are currently waiting for the sqlite_async (Powersync) factory to initialize before showing the interactive UI to the users. At the moment we are comfortable with 5 readers, but that means that on app start we need to wait for the initialization of all the readers in the pool (about 1.3 s on my emulator). If we use 1 reader, time is reduced to 500 ms.
What we were thinking is if there could be a way to open with 1 writer / 1 writer + 1 reader, and then have some way of adding more readers at runtime.
We would open the app as thin as possible and then asynchronously spawn the other readers when the user can interact with the UI.
Thanks!