The thing to remember here is that the datastore stub is that: a stub. The whole thing gets loaded into memory. That's how we're able to determine what indexes are required, do full datastore scans, etc.
-- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Sun, Jul 31, 2011 at 5:17 PM, Richard Arrano <[email protected]>wrote: > Thanks Tim, you nailed it. I attributed it to 1.5.2 but I realized I > created a moderate amount of data around the same time, hence the > slowdown. Using SQLite fixed it completely. Thanks! > > -Richard > > On Jul 31, 4:52 pm, Tim Hoffman <[email protected]> wrote: > > --usesqlite > > > > If you datastore gradually grows and you keep adding to it then it will > get > > really slow. > > The 1.5.2 unless you use --default_partition argument you end up with a > > different namespace so > > the datastore may appear empty (you can't find any data) so you chuck > some > > more data in and > > boom your datastore is twice as big as it was before. > > > > Just a guess mind you. > > > > Rgds > > > > Tim > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
