I read somewhere that IN queries are processed serially by the
datastore. GOOGers, what is a rough rule-of-thumb on the benefit of
using IN? For example, if the base RT latency for anything with the
datastore is Nms, then could guesstimate that using N for a list of 3
is not a huge latency win, but using IN for 10 is. Does using IN
substantially cut down on the api_cpu_ms used vs sequential queries?

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to