3 ms·
This is a great point. I do love sqlite, it really is awesome, but you had better need what it provides, since you are taking a 50x performance hit versus simp
by watmough 11y ago
This is a great point.
I do love sqlite, it really is awesome, but you had better need what it provides, since you are taking a 50x performance hit versus simply dumping an object tree to a binary file.
If anyone is interested, I could try and dig up my notes from switching from sqlite to NSArchive.
- Something1234 11y agoI would be interested in those notes.
- watmough 11y agoSorry, I simply haven't been able to find them. However, the upshot was that in my FemCal app, loading several months of entered fertility cycles went from 100's-1000's of milliseconds to just a few 100's. The overall speedup when loading was about 50x, when using NSArchive versus sqlite3. Neither implementation was or has been optimized, though I did try to write the sqlite3 code as efficiently as possible, since it was clearly a source of slowness from day 1.