[Mongrel] Server timeouts
pete at nextengine.com
Fri Nov 2 14:38:30 EDT 2007
Yeah, all the foreign keys are indexed. I'm also caching what I can
in our ruby app's memory.
It seems to be the database writes that are taking up a lot of the
time. The other offender are some multiple JOINs we're doing.
I've ordered more processors for the database server, and am clearing
off a second machine so I can get a little MySQL cluster going. Any
advice on this is welcome since I've never scaled a database server
As the database gets faster, it will help reduce the timeouts. But
demand + server load has a way of sneaking up on you. I'm looking
for a way of making sure our server is less likely to timeout on
users when we run into system bottlenecks (now + in the future).
On Nov 2, 2007, at 11:29 AM, barsalou wrote:
> What about the DB is the bottleneck? I'm assuming you have already
> looked at indexing and the like.
> Mike B.
> Quoting Pete DeLaurentis <pete at nextengine.com>:
>> Hi guys,
>> Does anyone know if mongrel has a built-in timeout for requests that
>> take too long? If so, how do you increase it?
>> I've found that some server requests are timing out. Complicated
>> requests are already being farmed out to asynchronous processes. But
>> some of the more basic requests are timing out when we have our peak
>> server load in the mornings (the bottleneck is the database server).
>> There are a couple possible locations for the timeout I'm seeing:
>> 1. Mongrel
>> 2. Lighttpd
>> 3. Client browser / application
>> On my local development server, it does not timeout, leading me to
>> believe it's not #3.
>> Any feedback is appreciated.
>> Mongrel-users mailing list
>> Mongrel-users at rubyforge.org
> This message was sent using IMP, the Internet Messaging Program.
More information about the Mongrel-users