<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Kirk Haines wrote:
<blockquote
cite="mid:f4cd26df0710030818w3d745c41u37fc15e3cf3ee9c5@mail.gmail.com"
type="cite"><br>
<pre wrap="">
evented_mongrel will let you queue up lots of requests without
incurring the RAM and performance killing overhead of threads in
Mongrel.
</pre>
</blockquote>
I'm worried about queuing.<br>
<br>
I'm working to remediate a Rails app ( not mine ) that can take as
long as a minute to generate certain pages.<br>
<br>
Consider the case where mod_proxy_balancer sends a request to an
application server that's 1 second into a 60-second rails page. With
queuing, wouldn't the second request sit in the queue for 59 seconds
while waiting for the first request to complete?<br>
<br>
The current workaround is to have a hundred of Rails app server
instances chewing up huge amounts of RAM. I would quite happily trade
that in for the memory and performance overhead of whatever
multiplexing or multithreading scheme is used in the app server. All
I need is a guarantee that the app server will not call select if 1)
it's already working on a request and 2) it won't open and close a
socket for a request it's not prepared to handle. If the app doesn't
call accept() Apache will gracefully move on to another app server.<br>
<br>
<br>
<blockquote
cite="mid:f4cd26df0710030818w3d745c41u37fc15e3cf3ee9c5@mail.gmail.com"
type="cite">
<pre wrap="">Swiftiply with swiftiplied_mongrel will load balance your slow
requests across your backends optimally, with no crowding on any one
backend, while again ensuring that you don't have RAM and performance
killing overhead of threads in Mongrel.
</pre>
</blockquote>
I'll look at swiftiply -- this is the first I've heard of it.<br>
<br>
Tusend tak and <font color="#000000"><strong>どおもありがと,<br>
</strong></font><br>
- Rob Mela<font color="#000000"><strong><br>
<br>
</strong></font>
</body>
</html>