Remember that every single property (well excepting blob/text) has 2 indexes - automatically, unless you explicity say that a property is to be unindexed.
Then again 1.5G is only $5-6 a year, even using the high replication datastore. To reduce the storage use, could set properties to be unindexed. But would have to loop over all the entities and re-put them. Probably end up costing you more than just keeping them. On 24 May 2011 14:17, Plumo <[email protected]> wrote: > hello, > my app has 396MB of entities but is using 1.48GB of storage. I understand > this may be because the indices add a lot of overhead. > I have 1 index: category ▲ , state ▲ , title ▲ > and 1 big table: > > title: string > category: int > address: string > city: string > state: int > zip_code: string > country: string > telephone: string > website: string > menu: text > latitude: double > longitude: double > source: string > created: datetime > updated: datetime > > Any advice how to reduce this excessive storage overhead? > Richard > > -- > 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.
