For the past two days, the datastore's query latency has been very high--over 1300ms in some cases. Since it doesn't support joins, multiple sequential queries will sometimes be need. That latency can really add up...
I suspect appengine has been a victim of its own success; there seem to be many more performance problems today than there were six months ago. Perhaps it's time to raise the prices, change the pricing structure, or invest in more hardware? On Mar 8, 5:21 am, Alexander Lagler <[email protected]> wrote: > first of all i thinks this is not common! > > do you have 201 single selects with opening and closing the > persistence manager all the time? > > can you give an quick overview over the structure your code has? > > with 201 objects i would do it like this: > > getting all "rooms" with one query > getting all "tables" with one query > getting all "games" with one query > > then putting them together with <room,List<table>> and > <table,List<game>> or <room,<List<table,List<game>>> generics or > something like this to simulate a tree structure. > > how large are your objects? do they contain massive text or blob data? > > 200 objects are really not too many... > > hope this helps > alex > > On Mar 8, 1:08 am, nicolas melendez <[email protected]> wrote: > > > > > Hi there, i have an entity group thish tree is like this: > > > Room --> Table --> Game > > > in an operation i need to retrive the whole tree, which are 201 entities > > and take me 2688 ms and that is a lot of time! > > That is common in app engine, or i am doing something wrong? > > > Thanks in advance > > NM -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. 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-java?hl=en.
