Hi, Yes, the tree is indeed serialized for access. This would be a problem with simultaneous score updates from many users.
Now, to improve the ranker, wouldn't it be better to use the same tree structure(the N-ary tree used by ranker) for assigning the parent entities for the nodes? Say my score update would modify only the leaf node. So for this update it would lock only the leaf node and its parent? Regards, Indraneel On Jan 29, 11:42 am, morten <mor...@fusemail.com> wrote: > Hi > > Is it correct that the ranker code results in a tree where all the > nodes in the tree is stored within the same GAE entity group (they all > have the rootkey as parent), resulting in the entire tree being > serialized for access? > > Best regards, > Morten Nielsen > > On Jan 26, 11:08 pm, ryan <ryanb+appeng...@google.com> wrote: > > > thanks for pinging us! they were actually ahead of me on this, and > > they published that library a while back: > > >http://code.google.com/p/google-app-engine-ranklist/ > > > we'll probably post something about it to the app engine blog soon. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
