On Tue, Dec 2, 2008 at 4:20 PM, Amir Michail <[EMAIL PROTECTED]> wrote:
>
> On Tue, Dec 2, 2008 at 3:08 AM, Amir Michail <[EMAIL PROTECTED]> wrote:
>> On Tue, Dec 2, 2008 at 3:07 AM, Greg <[EMAIL PROTECTED]> wrote:
>>>
>>>> When doing a urlfetch, it may take quite a long time. As this is not
>>>> a CPU usage issue, what's the point of limiting the request time
>>>> anyway? Why not allow the request to go on for a minute or so?
>>> Because it ties up memory for the duration of the request. Imagine if
>>> they allowed hour long requests - it would be easy to swamp machines
>>> with requests waiting for a response.
>
> Or just handle it with some sort of memory quota.
It's not just memory, it's also the fact that threads are also
waiting. And there are only a limited number of threads that can be
created and can be waiting at any time.
If all of your threads are waiting, even for a single minute, then no
other requests can be served in the meantime. Then, at peak, more
requests will come in which will have to be queued. Ad infinitum:
you'll end up with HTTP requests which have to timeout because there
aren't any threads available to handle them.
--
JM Ibanez --
The worst government is often the most moral. One composed of cynics
is often very tolerant and humane. But when fanatics are on top there
is no limit to oppression.
-- H. L. Mencken
-----
http://www.livejournal.com/~jmibanez/
httitp://www.mycgiserver.com/~butiki/
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
