[google-appengine] Re: db.get() on a list of keys being split into multiple get_async() calls as opposed to a single get_async() call

2011-12-07 Thread Bryce Cutt
I think the reason each call is listed as taking that long is that the
code makes all of the asynchronous calls and then asks for results
from all of them at the end. The 300ms is the time it took to get
results plus the time it spent waiting (hence the low API time and
high real time).

I am not sure if they changed the way it works or if they just change
the way it is reported. It appears to take the same amount of wall
time as before and the cost is the same as it is still costing us a
read per entity.

- Bryce


On Dec 6, 5:40 pm, Petey brianpeter...@gmail.com wrote:
 I'm seeing the same issue and it's not because production gets every
 entity. If that were the case then my app stats would show response
 times for each get around 10ms because that is about what our single
 gets usually take. Instead I'm seeing more like 300ms per get it is
 doing, which is what the previous response time was for the bulk get.
 And now it's showing several datastore_v3.Get calls in app stats that
 are taking ~300ms each. We haven't changed our code and it just showed
 up recently. Previously those 10 datastore_v3.Get calls in app stats
 showed as one call. So either app stats is displaying things
 differently or the bulk get is actually being called multiple times
 when it only should be called once.

 On Dec 3, 5:48 am, Timofey Koolin timo...@koolin.ru wrote:







  Production get every entity too. But do it in parallel mode - at the same 
  time.

  2011/12/3 Bryce Cutt pandas...@gmail.com:

   Did the production server change the way it handles a db.get() on a
   list of keys? I believe it used to do a single get_async on the list
   of keys but now it appears that it is doing a get_async for each key
   (according to appstats). The development server is still doing a
   single get_async for the entire list.

   --
   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 
   athttp://groups.google.com/group/google-appengine?hl=en.

  --
  Blog:www.rekby.ru

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



[google-appengine] Re: db.get() on a list of keys being split into multiple get_async() calls as opposed to a single get_async() call

2011-12-06 Thread Petey
I'm seeing the same issue and it's not because production gets every
entity. If that were the case then my app stats would show response
times for each get around 10ms because that is about what our single
gets usually take. Instead I'm seeing more like 300ms per get it is
doing, which is what the previous response time was for the bulk get.
And now it's showing several datastore_v3.Get calls in app stats that
are taking ~300ms each. We haven't changed our code and it just showed
up recently. Previously those 10 datastore_v3.Get calls in app stats
showed as one call. So either app stats is displaying things
differently or the bulk get is actually being called multiple times
when it only should be called once.



On Dec 3, 5:48 am, Timofey Koolin timo...@koolin.ru wrote:
 Production get every entity too. But do it in parallel mode - at the same 
 time.

 2011/12/3 Bryce Cutt pandas...@gmail.com:

  Did the production server change the way it handles a db.get() on a
  list of keys? I believe it used to do a single get_async on the list
  of keys but now it appears that it is doing a get_async for each key
  (according to appstats). The development server is still doing a
  single get_async for the entire list.

  --
  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 
  athttp://groups.google.com/group/google-appengine?hl=en.

 --
 Blog:www.rekby.ru

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