You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First I faced this notable speed difference on iOS on simple select queries - C++ was about 4 times faster than KMM implementation using SQLDelight.
So I decided to prepare a test including bulk inserts and selects for both C++ and KMM with 100 000 records, results are: for inserts C++ is ~5 times faster than KMM, for selects C++ is ~7 times faster than KMM.
I prepared a test project with both implementations here
Is there something to do to improve SQLDelight performance? Maybe some tuning which I'm not aware of? Or is it generally a Kotlin issue?
The text was updated successfully, but these errors were encountered:
i assume this is the nature of kotlin native and there is nothing we can do to speed it up. Even if it is a sqldelight thing the actual issue would be (sqliter)[https://github.com/touchlab/SQLiter] since that is the native sqlite implementation, and kevin could provide more insight over there. At least from SQLDelight's perspective we're just executing strings, theres probably room for improvement but the best would be comparisons on the jvm since then we're not introducing separate runtimes that could be causing the issue
First I faced this notable speed difference on iOS on simple select queries - C++ was about 4 times faster than KMM implementation using SQLDelight.
So I decided to prepare a test including bulk inserts and selects for both C++ and KMM with 100 000 records, results are: for inserts C++ is ~5 times faster than KMM, for selects C++ is ~7 times faster than KMM.
I prepared a test project with both implementations here
Is there something to do to improve SQLDelight performance? Maybe some tuning which I'm not aware of? Or is it generally a Kotlin issue?
The text was updated successfully, but these errors were encountered: