SQLITE_BUSY in KMP Project

[thisisalexmcgregor]

Version

4.3.3

Summary

Hi!

This only happens for iOS but, in a KMP project Android is able to access an SQL DB but iOS gets the below error.

• Enabled WAL (Write-Ahead Logging) mode for better concurrency. Didn't result in any noticeable improvement.
• Added a new Database dispatcher with single-threaded execution (limitedParallelism(1)). No improvement that I could see.

LMK if you have any questions.

Logs

executeNonQuery error | error code SQLITE_BUSY
co.touchlab.sqliter.interop.SQLiteExceptionErrorCode: executeNonQuery error

[martinbonnin]

Thanks for sending this. This rings a bell.

If I remember correctly, there are a couple issues about this in the repo but I don't think we have ever managed to reproduce consistently.

Does this happen all the time or is this something you see in crash logs?

[thisisalexmcgregor]

On iOS it happens 100% of the time, on Android it doesn't happen. I'm using Combine and SKIE . To rule out SKIE I wrote a unit test around it's toPublisher() extension and sent it a ton of emissions and didn't get any sort of performance bottleneck.

Eventually I do get the payload I'm fetching but, it takes a couple of seconds. If I just store the responses in memory it only takes half a second or less.

[martinbonnin]

Thanks for the follow up! Having a reproducer somwhere would be super useful if you have something around?

Something else you can try is switching to the new cache: https://github.com/apollographql/apollo-kotlin-normalized-cache. It stores data as binary blobs and has been measured to be significantly more performant. Maybe that could do it.

[thisisalexmcgregor]

I'll take a look at that! Project isn't open-sourced unfortunately and I don't have a sample app demonstrating this just yet.