On Fri, Jul 1, 2011 at 10:16 AM, Sergey Schetinin <[email protected]> wrote: > On 29 June 2011 07:57, Ronoaldo Pereira <[email protected]> wrote: >> >> Also, on a spike in traffic today I got 70 instances up and running for >> around 30 minutes (Java app without threading yet...). This gives around 70 >> instances * (30+15 minutes) = 3150 instance hours = $252. > > That's 3150 instance-minutes = 52.5 instance-hours = 4.2USD or 2.625USD at > reserved pricing
Also, I think the 15 minutes is a floor. So it's just 30 minutes per instance. BTW one thing to keep in mind when talking about datastore operations is that this really isn't a fundamental change to the way things are priced now. If you look closely at request costs you'll notice there are already a lot of magic numbers (for example, an index write is always 17 cpu_ms). The new pricing of datastore ops just makes the magic numbers more explicit. And, it would seem, more expensive. So... the question of whether to fetch one big entity vs lots of small entities is something you have to deal with already. New datastore pricing doesn't change this. To save $$ and wall-clock time, you should denormalize your data structures and utilize memcache now. Jeff -- 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.
