Hey Andreas, It sounds like you're talking about the difference in your storage quota used and the total size of entities in your datastore statistics. That difference could be due to indexes, unfortunately indexes aren't included in the datastore stats. Star issue 2740. http://code.google.com/p/googleappengine/issues/detail?id=2740
Also, the counts and statistics aren't realtime. They may be delayed by a day. Your blobs and tasks also count against the stored data quota. The main spots you need to consider entity groups are queries. By default, db.gets by key are always strongly consistent. You'll need to decide if your queries need strong consistency or not. If you give us some details, I'm sure someone will offer some design ideas. Robert On Jun 18, 2011, at 6:28, andreas schmid <[email protected]> wrote: > hi, > > i wrote a python app before the high replication datastore was introduced and > i don't use entity groups like in the tutorials for the hr datastore. > i deployed this app with some test data to a hr appid and i see that i have > 1,5gb of stored data but only 0,4gb of high replication data. > what does that exactly mean? > > will it work as it did on the master slave but it will not use the hr > datastore? will i have issues with inconsistent data? > > thank you > > -- > 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.
