Google Appengine large amount of index data (python)

Question

We've just outgrown our free data usage quota in AppEngine which is great but looking at our data breakup, only 200M of the 1G is actual data / meta-data (still can't believe they pin you for that one) and the rest I assume is indexes from reading the help forums. Does anyone know if this is normal and if not are there any good tips to reduce the size of the indexed data?

Cheers, Richard

Who would you have Google charge to store the indexes, instead? — Nick Johnson
– Nick Johnson, Commented May 16, 2011 at 0:49
Happy to have the charges for indexed data just wandering if I've made some poor design decisions. With our 1GB of used data, only 200MB is actual data (not indexes) and of that 53% is meta data - it seems like I must be doing something wrong if only 10% of our data usage is actual data. — probably at the beach
– probably at the beach, Commented May 16, 2011 at 10:20

Matic · Accepted Answer · 2011-05-10 10:17:12Z

3

Depends on what you are storing in it. We've got 32GB of String/Integer/Text data, 181GB of indexes/meta-data and 812GB of blobs (we are storing a lot of small images). So it really depends on your queries and settings.

You can run

   appcfg.py vacuum_indexes .

to vacum indexes (remove unused stuff).

GAE automatically creates simple indexes for all properties, but you can disable them by adding

    indexed=False

on the property. See http://code.google.com/appengine/docs/python/datastore/propertyclass.html

answered May 10, 2011 at 10:17

Matic

4842 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Google Appengine large amount of index data (python)

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related