From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: 2.4 Success story
Date: Tue, 18 Sep 2001 12:20:03 -0700 (PDT) [thread overview]
Message-ID: <20010918192003.5C326783ED@mail.clouddancer.com> (raw)
A brief note of _thanks_ to all that create the linux kernel.
Mid-morning, I checked on a database fetch that has occaisonally
gotten out of hand and overrun the system -- depending on the kernel
version. It was overrun but this time, it was probably due to a
change I made in the fetch code yesterday.... but the _real_ issue is
that this is the first time I have ever had a very responsive system
under a load of 13+ and a couple hundred processes. There have been
countless times in the past that getting control when the system load
has gone past 6-7 was nearly impossible.
I was completely amazed and spent about 30 seconds to tame the rogue
processes, with system access feeling just like normal load
conditions.
This particular gem of a kernel is:
2.4.9-ac10 #1 SMP Tue Sep 11 21:47:15 PDT 2001 i686
THANKS!
I'd suggest that those running large applications experiencing
problems in transition from 2.2 -> 2.4 give this kernel a try.
next reply other threads:[~2001-09-18 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 19:20 Colonel [this message]
2001-09-19 19:33 ` José Luis Domingo López
2001-09-19 22:23 ` Jeffrey Ingber
2001-09-19 22:43 ` Alan Cox
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=20010918192003.5C326783ED@mail.clouddancer.com \
--to=klink@clouddancer.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
Powered by JetHome