There are really two issues at play here: detecting which of your indexes are under-used, and detecting which indexes are absolutely not used. The first is a matter of profiling, monitoring, logging from your own side, and the second is a matter of running appcfg.py vacuum_indexes to delete any indexes which aren't explicitly mentioned in index.yaml (that is, any indexes which you didn't explicitly code for).
You could make a Feature Request in the Public Issue Tracker <https://code.google.com/p/googleappengine/issues/list> for something which could help with this, such as collection of statistics in the Developers Console as to how often an index gets hit in a given time period. On Wednesday, January 13, 2016 at 10:50:16 PM UTC-5, A. Kong wrote: > > Hi all, > > Over time I have a number of indexes in the index.yaml . Some of them may > be no longer needed because over time my application ceases to make a > certain query. > > Is there an easy way to identify unused indexes? > > Cheers > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/926d6bc6-89a4-496f-bcd5-e6b1d7ee2465%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
