sounds like a scheduler issue
did you try "deadline"?
on Linux systems pass "elevator=deadline" as kernel param
Am 12.10.2013 20:58, schrieb Chris McKeever:
> We had a similar issue a bit back - and although it sounds similar - based
> on your followups it probably isnt, but will just toss this out there
> anyhows. We were experiencing connection timeouts when load would ramp up.
> Doing some digging we learned that our firewall between the servers
> bandwidth would get consumed by a large wordpress load - and this in
> essence backed up the rest of the requests until they timed out.
> We fixed that load issue which reduced the data passing through and have
> expereinced a significant performance boost in our app let alone reduction
> of these timeout issues
> On Sat, Oct 12, 2013 at 12:56 PM, Reindl Harald <h.reindl@stripped>wrote:
>> Am 12.10.2013 19:45, schrieb Jørn Dahl-Stamnes:
>>> On Saturday 12 October 2013 17:36, Reindl Harald wrote:
>>>> so someone did "optimize table" on a large table
>>>> you do yourself not a favour restarting the server in such a moment
>>> 7 hours before the server was shut down, we did a alter table to add a
>>> key to a table that is read-only from the web application.
>> which means the table is most likely completly copied
>> in a temp file and depending on the table size this
>> takes time - you killed the alter table i guess
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc