timh@'s response is correct. by scattering the IDs we avoid overloading a Bigtable tablet and thus the associated latency.
-- Chris On Sat, May 25, 2013 at 10:53 PM, timh <[email protected]> wrote: > From my understanding sequential IDs, keys etc mean that data is written > into the same area (tablet). By scattering ID's they can more distributed > data and better concurrency. > > Maybe not the best description but thats my guess, Sequential values > have been discussed in the past with regards to indexes as well. > > T > > > On Sunday, May 26, 2013 2:12:44 AM UTC+8, Vinny P wrote: >> >> >> On Friday, May 24, 2013 7:04:08 PM UTC-5, Chris Ramsdale wrote: >>> >>> In the upcoming 1.8.1 release, the Datastore default auto ID policy in >>> production will switch to scattered IDs to improve performance. >>> >> >> >> Out of curiosity, what does "improve performance" mean? Faster datastore >> puts? Less variable times? Cheaper infrastructure costs? >> >> ----------------- >> -Vinny P >> Technology & Media Advisor >> Chicago, IL >> >> My Go side project: http://invalidmail.com/ >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
