Is each User a root entity (i.e. an entity with no parent) ? If so, then each User is its own Entity Group, and therefore you can sustain 1-10 requests/second of writes to each individual user. On Mon, Oct 19, 2009 at 4:01 PM, Diana Cruise <diana.l.cru...@gmail.com>wrote:
> > This is exactly what I'm am talking about...in my case the User and > UserAddr are both in the same Entity Group. So, are you saying that > my application which has a global presence in GAE can only support 25 > simultaneous Users performing this update in under 5 seconds? > > Again, I take 1-10 requests per second response and go with the avg of > 5/s. Add up 25 Users simultaneously hitting this Entity Group and > that consumes a full 5 seconds. So, if you have 25 Users doing the > same update over and over they will each have about a 5 second > response. > > I know I am wrong because this is way LOW for a Google platform or any > other...I just am NOT hearing or seeing numbers that say otherwise. > > If you clarify for me that this Entity Group performance stat of 1-10/ > s is granular to the Row then we're on to something... That would > tell me that my scenario above only applies if ALL Users were logged > into the same account!!! If the Entity Group performance stat is > granular to the Row then that would mean an infinite number of Users > would average 5 updates per second. Please tell me this is TRUE! > > Otherwise, if this Entity Group performance stat of 1-10/s is granular > to the whole group (is ALL rows) then the performance is dire as I > described originally. Please tell me it isn't so! > > On Oct 19, 11:10 am, Don Schwarz <schwa...@google.com> wrote: > > It's 1-10 updates per second per Entity Group: > http://code.google.com/appengine/docs/java/datastore/transactions.htm... > > > > You need to break your design up into Entity Groups according to which > > pieces will need to be updated in a single transaction. In the best > case, > > each entity can be its own entity group and the only restriction is that > you > > update each entity no more often than 1-10 times per second. > > > > For example, it would not be a good idea to store a global counter in one > > entity unless you planned to update it no more than 1-10 times per > second. > > The solution to this is to use sharded counters: > > > > http://code.google.com/appengine/articles/sharding_counters.html > > > > On Mon, Oct 19, 2009 at 11:06 AM, Diana Cruise <diana.l.cru...@gmail.com > >wrote: > > > > > > > > > > > > > Shawn, the 1-10s per Update was sited from Max Ross' I/O Video and > > > I've seen it in various talks/docs along the way... > > > > > On Oct 19, 11:03 am, Diana Cruise <diana.l.cru...@gmail.com> wrote: > > > > Shawn, the docs link you site is riddled with numbers (easy to get > > > > lost in them and what they truely mean)...which is why I included a > > > > simplest of scenarios above, that being to simply add a home > > > > addressbook entry attached to a User. Surely someone has a sizeable > > > > production system today in GAE that could share load results and real > > > > costs. If noone does, then that is also very troubling. > > > > > > Gaurav, I assume too that reading is NOT the problem and by this post > > > > am hoping to get real-world numbers to a simple update transaction. > > > > But, we need production app feedback from the most popular apps out > > > > there. Is there such a list for Java for GAE yet? Surely, there are > > > > large production apps by now? > > > > > > On Oct 19, 2:17 am, Gaurav <ano...@gmail.com> wrote: > > > > > > > GAE performs best for simultaneous read operations. So there could > be > > > > > virtually any no. > > > > > of users reading at the same time, no issue. But when it comes to > > > > > making updates > > > > > performance degradation is significant. > > > > > To get a better understanding of how gae performs under heavy load, > I > > > > > recommend > > > > > this video :http://www.youtube.com/watch?v=AgaL6NGpkB8 > > > > > > > On Oct 19, 7:09 am, Shawn Brown <big.coffee.lo...@gmail.com> > wrote: > > > > > > > > Hi, > > > > > > > > > I have read that a particular User can process 1-10 request per > > > > > > > second. Is this a limit of the free quota or does paid quota > also > > > > > > > have this limitation. > > > > > > > > Where and what did you read? > > > > > > > > That doesn't seem consistent with the published limits. I guess > it > > > > > > depends on what they were doing with the app. > > >http://code.google.com/appengine/docs/quotas.html > > > > > > > > Shawn- Hide quoted text - > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
