It's barely an issue if your source can take Google's Request. Fetch from Google often clocks at 400 Mbps.
(I do 6M fetches a day) From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Joshua Bronson Sent: Wednesday, April 13, 2011 9:12 AM To: google-appengine@googlegroups.com Subject: [google-appengine] Re: urlfetch - deadline clarification + two issues One more urlfetch question: Unless I'm mistaken, it's not possible to begin streaming a urlfetch response to the client until it's finished downloading. So in the worst case, you have to wait for up to 32MB to be downloaded into memory before you can begin streaming it. Would you consider an API that allows us to just pipe the socket to response.out, which would significantly reduce latency and lower memory requirements for this use case? Thanks for your consideration! -- 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. -- 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.
