@Константин, you don't need to set "indexed = true" to get default indexes, if you don't set "indexed = false" you get the a default index on the property anyway.
@David, You can specify index direction on custom indexes (http://code.google.com/appengine/docs/python/config/indexconfig.html) just not on default ones, I think. My datastore is M/S (not HDR) and I don't use the Pipeline library. The Logs Storage doesn't seem to be related either -- I've got another app with an even smaller log storage size that also shows as 100% of the Total Logs Storage for Version on the Logs section and its datastore size value on the Quota Details is within the expected bounds. In the meantime I've updated the application with the 1.6.4 pre-release SDK (https://groups.google.com/d/topic/google-appengine/JKC07lp8q5g/discussion), since it's supposed to show the indexes size on the Statistics. Can't find them there for now but their last update might not be recent enough. I'm also waiting for the Billing History report for the 23rd because that's when, apparently, the datastore size jumped to 1GB (or at least when I noticed it). For the previous days the datastore storage value on the Billing History usage reports is always 0.02GB. Thanks everyone for the support. On Saturday, March 24, 2012 12:11:47 PM UTC, David Hardwick wrote: > > Is it really two indexes for both asc and desc for each simple > property that is indexed? If so, then it would be great if we could > specify if we only wanted ASC or only DESC to sames some unwanted > writes. > > With HRD and indexing, the writes add up real quick (especially using > the Pipeline library[1]) > > rock on, > -hardwick > > [1] - > http://code.google.com/p/appengine-pipeline/<http://code.google.com/p/appengine-pipeline/> > > > > On Mar 23, 12:45 pm, Jeff Schnitzer wrote: > > If you have not optimized your indexes, they will almost always > > account for the bulk of your data storage. > > > > Most of the datastore APIs (python db, ndb, java low-level, jdo/jpa, > > etc) default to creating two indexes (asc and desc) on every property. > > Each of these index entries represents another row in a BigTable > > tablet; for small entities, each of these rows are only slightly > > smaller than the master blob. So 5 indexed properties could easily > > cause a 5-10X expansion in your total stored data volume. > > > > You can't vacuum these indexes; unlike multi-property indexes defined > > in datastore-indexes.xml/yaml, single-property indexes are established > > when you save an entity and are only deleted by resaving the entity. > > > > If you are concerned about space (or datastore write operations), you > > should go through your data model and flag any properties you aren't > > querying on as unindexed. Then you will need to resave your entities > > to reclaim index space. > > > > Jeff > > > > > > > > > > > > > > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/cntJWnN_aMkJ. 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.
