From: "Michael Frank" <mhf@linuxmail.org>
To: "Lawrence Walton" <lawrence@the-penguin.otak.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: server migration
Date: Sun, 07 Mar 2004 20:21:03 +0800 [thread overview]
Message-ID: <opr4hq9dmf4evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <200403071231.50912.vda@port.imtp.ilyichevsk.odessa.ua>
>> > On Friday 05 March 2004 20:13, Lawrence Walton wrote:
>> > > Hi all!
>> > >
>> > > I tried about four months ago to migrate a busy server to 2.6.0-test9,
>> > > and failed miserably. Lightly loaded it worked well but as the number
>> > > of users increased, the number of processes in uninterruptible sleep
>> > > increased to the hundreds and then the server fell on it's face. I
>> > > never found out exactly why or what processes where hanging if I
>> > > guessed it would be openldap.
-Test9 was the "oddest" kernel I ever ran (since 2.2.x) - even got it
repeatably to hardlock lock by loading it a bit with dd ;)
Since then, Nick Pigin has put a hell of an effort into the
anticipatory scheduler and much else all over has been refined too.
I have done a bit of stress testing of io, network and cpu and
IMO, 2.6.3 will perform nicely in a server environment and there
will be no significant problems.
Input from production use is essential though and it would be much
appreciated if you would go for it :)
Regards
Michael
prev parent reply other threads:[~2004-03-07 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 18:13 server migration Lawrence Walton
2004-03-05 18:21 ` Danny ter Haar
2004-03-08 21:50 ` Mike Fedyk
2004-03-06 23:33 ` Denis Vlasenko
2004-03-07 1:35 ` Lawrence Walton
2004-03-07 10:31 ` Denis Vlasenko
2004-03-07 12:21 ` Michael Frank [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=opr4hq9dmf4evsfm@smtp.pacific.net.th \
--to=mhf@linuxmail.org \
--cc=lawrence@the-penguin.otak.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox