My site's typical page is like this: http://www.v2ex.com/t/7577
As you have seen, a topic with dozens replies, each reply carry 3 entities: reply, member and avatar. And there are other supporting dynamic elements on the page (most of them can be cached). But when someone replied to the topic, then it will trigger a lot memcached objects to be removed. For hot topics, memcached objects can just survive minutes or even seconds. And there could be 100+ or even 1000+ entities on one page. If I knew they're going to charge datastore reads/writes, I may think another way to write the code. But now, it's too painful to rewrite the whole site. -- 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/-/0dfGjryGNWwJ. 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.
