3 ms·
> It's not as efficient for peak hours. Actually it's quite fine during peak hours. You could, however, say it's a waste of resources during the lull times.
by wvenable 17y ago
> It's not as efficient for peak hours.
Actually it's quite fine during peak hours. You could, however, say it's a waste of resources during the lull times. But I'm not using those resources for anything else anyway; the entire purpose of the server is to service web requests. If a bunch of processes are sitting there wasting memory being idle, that's not a problem.
> There are several use-cases I can think of, the simplest being more than one blocking request for rendering your page
That's a fair case but I haven't personally encountered it yet. A good example, however, would be building a mashup page of content from a bunch of different web services.