Databases
StackOverflow2013
Postsdbo
POAndroid SQLite Performance with Indexes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid SQLite Performance with Indexes
    primarykey
    data
    text
    <p>My Android app works by using a SQLite database that is generated on the user's PC and transferred to the device. It all works, but I had not anticipated the number of users who would have really huge amounts of data. In these cases, the UI is very sluggish as it waits for the data to be fetched.</p> <p>I've tried a number of tricks that I was "sure" would speed things up, but nothing seems to have any noticeable effect. My queries are almost all very simple, being usually a single "col=val" for the WHERE clause, and INTEGER data in the column. So I can't do much with the queries.</p> <p>The latest, and I am not an SQL expert by any means, was to use "CREATE INDEX" commands on the PC, believing that these indexes are used to speed up database searches. The indexes increased the size of the database file significantly, so I was then surprised that it seemed to have no effect whatsoever on the speed of my app! A screen that was taking 8 seconds to fill without indexes still takes about 8 seconds even with them. I was hoping to get things down to at least half that.</p> <p>What I am wondering at this point is if the SQLite implementation on Android uses database indexes at all, or if I'm just wasting space by generating them. Can anyone answer this?</p> <p>Also, any other things to try to speed up access?</p> <p>(For what it's worth, on an absolute basis the users have nothing to complain about. My worst-case user so far has data that generates 630,000 records (15 tables), so there's only so much that's possible!)</p> <p>Doug Gordon GHCS Systems</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDoug Currie
    1. USgordonwd
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid SQLite Performance with Indexes
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAndroid SQLite Performance with Indexes
      1. USBehrang
      1. VTFavorite
    3. VO
      singulars
      1. POAndroid SQLite Performance with Indexes
      1. This table or related slice is empty.
      1. VTUpMod
    1. COpost some slow queries, along with table definitions and index-definitions
      singulars
      1. POAndroid SQLite Performance with Indexes
      1. USMikpa
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload