On Sun, Sep 7, 2008 at 10:38 PM, Scott K.
this is a 512MB RAM and 1024MB swap slice from slicehost.com.
4 64-bit AMD cpu’s.
Does this slice also runs the database?
some of index views on controllers pages take .5 - 1 second to load.
This is the problem, having request that take up to a second to be
serviced is too much. You are getting a lot of queued requests.
the weird thing is that now i can’t even get my web services to stay up
for 10 minutes without it starting to timeout which makes me think
something weird is going on. this site has been running for well over a
month without any crashes. do you think this could be related to the
hardware underlying on the virtual slice?
Your hardware should be fine for a moderated load (whatever “moderated”
You need to pin point why your request are taking so long to be
the site is wlodb.com if you want to take a look at how long it takes
(unless i just restarted the services).
how should i check how long the DB queries are taking? should i turn on
verbose logging in mysql? I have on slow query logging but haven’t seen
With INFO (default for production) you should be ok, look at this
Completed in 0.06489 (15 reqs/sec) | Rendering: 0.05481 (84%) | DB:
0.00109 (1%) | 200 OK [http://:/logi
If things are OK, time spent on DB should be a little fraction of the
total and rendering should take most of the time.
You need to assure at least a a dozen request per second (in my
experience) to offer a smooth operation.
thanks for the help so far!
You are welcome.
i have even tried to switch to a mongrel cluster but have the same
Thin and Mongrel, are architected in different ways. You real problem
is the slow actions.
You can try adding another thin/mongrel but while you have
controller/actions taking up to a second to service a request you will
be in trouble.