Here is an article that can help you reduce the # of composite indexes you use in some cases: http://code.google.com/appengine/articles/indexselection.html
On Tue, Nov 8, 2011 at 4:16 PM, Jeff Schnitzer <j...@infohazard.org> wrote: > FWIW, your app would have been a problem under the old pricing model > as well. The only difference WRT the datastore is that instead of > being charged "datastore operations" you were charged a magic number > of "api_cpu_ms" per operation. The pricing model is pretty much the > same, it's just more expensive. > > If you're churning through your datastore ops because you have 100 > indexes, you would have churned through your CPU quota before. The > problem is you're trying to update too many indexes. The only > solution is "don't". > > BTW you only incur costs for index changes; if you re-put an entity > without changing the index, you don't get charged for an index update. > > Jeff > > On Tue, Nov 8, 2011 at 4:01 AM, Kenneth <kennet...@aladdinschools.com> > wrote: > > I hear what you're saying, but at that rate I'm pretty much rewriting my > > application plus cost isn't even known. And I like the datastore. > > The problem as always is how the app was written. Users can update one > > field at a time on a data grid and save it back via ajax, so that's > > seriously not efficient from a cost pov if they're doing a few fields. > The > > model they're writing to has more than 100 indexes (property indexes both > > directions + composite indexes). So I need to look at de-indexing fields > > and removing composite indexes given some of the datastore goodies that > have > > come on stream in the past year. There's also a problem with another > model > > with 3 large key lists that's written a lot. I don't know how the cost > on > > that is even calculated tbh. > > The fundamental problem is I lack numbers on how much each request is > > costing me so I don't know where to focus my efforts. It's mostly > guesswork > > and intuition. There could be a big elephant I'm missing. > > I'd really love to pre-purchase datastore operations in the same vein as > > instances. > > > > -- > > 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/-/Wgyduglk9KMJ. > > To post to this group, send email to google-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
