I know this is an old thread, but relevant to a recent topic of interest. My question is:
If the sustained QPS is indeed high, is there any advantage to doing batch put operations (as it relates to the 'hot tablet' issue with sequential index values)? In other words, if I am trying to write 1000 entities/second using timestamp as an indexed property, will batching them into groups of 250 or 500 also batch the index row writes that are going to the 'hot tablet', thus mitigating the problem to some extent? On Friday, February 19, 2010 10:51:06 AM UTC-5, Nick Johnson (Google) wrote: > > Hi peterk, > > On Fri, Feb 19, 2010 at 2:02 PM, peterk wrote: > >> Say I did a batch update of 500 entities all of the same model...could >> this breach the '100s of qps' requirement that could lead to tablets >> getting too hot? I've seen benches (http://blog.dantup.com/pi/ >> bm_put_perf.png <http://blog.dantup.com/pi/bm_put_perf.png>) that show >> 500 entities being batch put in ~4s which >> suggests an average put rate that might be in the 100+ per second in >> such a case. >> > > Only if you're doing such puts at a high rate. It's the sustained rate > that matters, not the instantaneous rate. > > -Nick Johnson > > -- 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/-/yFXr9D7jXicJ. 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.
