Reads can be cached through the memcached service, and memcached hits are free.
If you try GAE, I would highly recommend re-examining your architecture to make optimal use of GAE's strengths. I haven't released my own app yet, but when I started I tried to use JDO, and the performance was awful. After switching to Objectify not only did my performance improve significantly, but nearly all the database reads disappeared due to the ease with which Objectify integrates with memcached. - Kris On Tuesday, September 13, 2011 4:03:10 AM UTC-7, Karel Crombecq wrote: > > Hey Jay, > > I did some calculations on my current database data, and CQ2 generates > about 1M database writes for something like 650 daily users. That's about 3 > times as much as your game does, which would also triple the bill. That's a > lot, but something I can handle. Since most of the writes are one-record > only, the total cost would be $1,5 per day for 1000 users. > > However, the datastore reads are the real issue here. I have about 4M > SELECT queries for 650 users. Considering that many of these return more > than one row, I can easily reach 10M datastore reads each day, for an > additional cost of $2,8 each day. > > -- 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/-/wPcLsjyzPIQJ. 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.
