and just so everyone knows, you can change this field after existing data is there and next time you put/write the entity the impact will be reduced. It is a good practice to always set indexed=False unless you know you need the single property index or if you want to use it in a composite index (index.yaml).
On Sep 1, 5:33 pm, Kaan Soral <[email protected]> wrote: > WOW, Im glad I took the time and added indexed=False to wherever > possible > > On Sep 1, 8:20 am, Robert Kluin <[email protected]> wrote: > > > > > > > > > Hey Mike, > > The difference is due to indexes. Every index write is a datastore > > operation too. So if your entity has five indexed properties, you've got > > another 10 datastore operations per entity written. > > > Robert > > > On Wednesday, August 31, 2011, Michael Robellard <[email protected]> wrote: > > > Dear Google, > > > > I love Google App Engine, but right now I am at a loss for what to do. > > > My current billing is $4.98/day. Under the new system it is $34.41/ > > > day, and that is with the 50% frontend discount. The effort that would > > > be involved in porting my app to a different architecture is far > > > beyond what I could accomplish in the next few weeks, and to be honest > > > I don't want to move off of App Engine. I like not having to deal with > > > Sys Admin stuff. > > > > I have to imagine that Google did not intentionally raise my serving > > > rates by 700%, so that must mean I am doing something wrong in my code/ > > > design, however I don't know how to fix these problems currently. I > > > have already done a lot of work in the past to memcache things and do > > > multiple gets and puts in a single call, and most of my apps time is > > > spent handling tasks. So I have already done a lot of what is > > > recommended in the managing resources guide. > > > > In addition I don't understand how my app says it has 1.05 million > > > reads and 12.3 million writes per day when I look at Appstats and see > > > that I have at least 3 datastore gets for every one datastore put and > > > that's not count next and runquery. > > > > Thanks, > > > > Mike > > > Railroad Empire > > > appid: railroadempire > > > > On Aug 31, 6:51 pm, smwatch <[email protected]> wrote: > > >> Is it really 10 times the original cost.!! Now we will be paying from > > >> $200/month to $2000/month under new billing. Just out of our reach, > > >> does not make any business sense to stay with GAE. > > > >> We spent huge amount of time and effort to learn and develop in > > >> Python, and now we are being forced to move out of Google Engine. This > > >> completely does not make any sense. > > > >> Google please respond, you are reading please give us more time to > > >> either move off your systems, or compensate for existing users. Giving > > >> a email notice of such a short duration and showing Preview of billing > > >> so late in the game is just not right. > > > >> Google please do the right thing to make this billing more gradual. > > > >> Developers all over, please help show your sentiment. > > > > -- > > > 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. > > > -- > > ------ > > Robert Kluin > > Ezox Systems, LLC -- 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.
