Hi David, Thank you for your detailed post. It is for a forum application. A topic may have up to 20.000 posts, set to 10 for each page. You can browse through the posts with the next and prev page buttons but we also need a jump to page n field.
For now, we store all keys in the topic entity. It is a blob with a serialized array with some magic to reduce the size. The forum entity does the same for all topics. We also have a ranking system to the list the active users. It is the entire ranking table divided in blocks of 50.000 users per entity @ 0.7MB. The table doesn't include users with a score of 0 posts. Didn't thought of the B-tree approach, will have second thought about it. -- 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/-/OtRVdXSgWOsJ. 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.
