<br><br><div class="gmail_quote">On Sat, Mar 22, 2008 at 3:39 AM, Dave Cheney <<a href="mailto:dave@cheney.net">dave@cheney.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div class="Ih2E3d"><br><div>On 22/03/2008, at 8:19 AM, Steve Midgley wrote:<br><blockquote type="cite"><span style="border-collapse: separate; color: rgb(0, 0, 0); font-family: -webkit-monospace; font-size: 10px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">If so, it seems like if one were using something like nginx fair proxy,<span> </span><br>
then the mongrel would be running it's garbage collection AFTER the<span> </span><br>client got all its html but BEFORE any new requests were sent to it.<br><br>In a fully loaded server it wouldn't matter at all, but most<span> </span><br>
environments have a little headroom at least, so that nginx fair proxy<span> </span><br>would just route around the mongrel that is still running a GC at the<span> </span><br>end of it's Rails loop.</span></blockquote>
<br></div></div><div>That would only be true if you set the connect timeout on the backend to 1 second AND your GC pass took longer than 1 second.</div></div></blockquote><div><br>Yes, but worse case here is that another request gets delayed before processing. Still potentially better (IMHO) than dealing with this delaying when processing a request.<br>
<br>- scott<br></div></div><br>