Thanks Randy! Then I'll use memcache straight ahead. On Friday, December 28, 2012 3:42:21 AM UTC+8, Randy Shoup wrote: > > In general, writing to memcache directly will be an order of magnitude > faster than queueing up a task with that data. The task queue will persist > your data in multiple disks and across multiple data centers for > reliability, while memcache will only write to memory in the local data > center. > > Both APIs support mechanisms to write asynchronously without blocking. > > On Thursday, December 27, 2012 12:22:09 AM UTC-8, Lawrence Mok wrote: >> >> I am wondering if I'm doing right. Could someone give me some comment on >> this: >> >> I have an application which need to write to memcache for all of the >> generated response. However I am guessing the act of "writing to memcache" >> would still spend time e.g. 50ms before it's done then the app engine send >> the completed http response back to client. >> >> What I do now is to call the task queue API to separate this "write to >> memcache" as an external task. Would this help speeding up the use-facing >> response time? Or actually writing to task queue is still slower than >> writing to memcache and is it still a blocking function? >> >> By the way, I'm using the "Go" language and the "Delay" package as >> described in >> https://developers.google.com/appengine/docs/go/taskqueue/delay >> >> >>
-- 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/-/1lE2Hn1sf6EJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
