Hi Jeff, Yes, it's really a concern. Previously fetching 20 small sequential entities cost about the same as fetching 1 large entity 20x the size of the small ones. Now it's costing 10-20x as much because of the per-read (and per write for puts) pricing.
I'm already using memcache extensively, but thanks for the suggestion in case I wasn't. It's a big help... assuming google doesn't start charging per get/put next year. I'm not keen on doing extra work either. But I think now is the time to do it. I'm refactoring a lot of other things to target the new billing realities. Startup times used to be a problem, now it's keeping idle instances unnecessarily. I might as well adjust the entity read/write load now while I'm up to my elbows in the code rather than have to come back in a year when it's not all fresh in my head. Cheers, Steve -- 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/-/WlNgjgAJJ20J. 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.
