You're limited to 200 indexes for a billing enabled app and 100 for a non-billing enabled application.
The number of indexes does not introduce a scalability cap, it just makes every write much, much more expensive. The question here is whether or not your budget can support this. On Sat, Jun 12, 2010 at 11:23 AM, Harshal <[email protected]> wrote: > Hi, > > Until Google releases the version which they showcased in I/O where we > won't have to deal with exploding indexes, I guess our choices are very > limited and we would have to live with it. > > I would like to go ahead and ask, what is acceptable number indexes people > have in general? I have an entity which has something like 42 indexes > (because I have to filter in various ways on many properties many times). Is > it scalable ? ( I am seeing high CPU spikes but I am fine with that, well at > least as of now). > > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- 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.
