Also... Is fillWindow called by the query? If not, then I don't see how performing the query on a background thread will help...
TIA. Marc On Feb 13, 7:34 am, Marc <[email protected]> wrote: > Great... Does this have to do with improving performance in > scrolling backward (since sqlite doesn't have functionality for > walking a result set backwards)? > > Thanks! > > Marc > > On Feb 12, 6:37 pm, Romain Guy <[email protected]> wrote: > > > We're aware of this issue :) > > > In the meantime, you should perform your query on a background thread. > > > On Thu, Feb 12, 2009 at 6:12 PM, Marc <[email protected]> wrote: > > > > I've noticed that the time it takes to enter my ListActivity is fairly > > > proportional to the number of items in the sqlite cursor. Indeed, > > > when I look at a trace, it seems as though fillWindow (i.e. filling > > > the cursor window) takes a HUGE amount of time when working with a > > > large cursor (one with thousands of rows). > > > > Does Android really load every single row into memory? How else to > > > explain literally seconds of time (not debugging) entering a list of > > > 2000 items (the time in fillWindow is minimal with a smaller list; > > > again, roughly proportional). > > > > Can anyone with an understanding of the internals help me out here? > > > > Thanks. > > > > Marc > > > -- > > Romain Guy > > Android framework engineer > > [email protected] > > > Note: please don't send private questions to me, as I don't have time > > to provide private support. All such questions should be posted on > > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
