The usual insert command in Android is slow, so we had to use a transaction and prepared statement. 2.0 Insert Speed Problemīut before we were able to efficiently insert the records to the database, we run into the problem of “insert speed”. All records were downloaded and inserted to the device SQLite database. We had to paginate the download, so in our case, we had 6 pages. But to be safer, I made it to 5,000 records per page. 7,000 records and our app was able to read and parse it all. So I tried some more test until I found the correct number of records per URL. I tried to parse it but failed, memory leaks occur, sometimes it was an out of memory error. Our Android app has to read, parse and store the data on the device SQLite database.ģ0,000 records in one URL load is not advisable, we did several tests. The data were from a URL with data in JSON format. I think that’s a lot of data for a phone app, but that’s the way our app is. Recently, my app was required to download 30,000 records during sync. This post will cover the following contents:ģ.0 Android SQLite Transaction Example Source Codeĥ.0 Other Tips On Improving Insert Speed 1.0 The Back Story I’m really excited to share this since it helped me a lot and maybe it can help some more people as well. Today I’m going to share an Android SQLite transaction example that I consider as one of the most useful test I made with Android SQLite.
0 kommentar(er)
