From: GrandMasterLee <masterlee@digitalroadkill.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Austin Gonyou <austin@coremetrics.com>, linux-kernel@vger.kernel.org
Subject: Re: Using O(1) scheduler with 600 processes.
Date: 24 Jan 2003 00:09:27 -0600 [thread overview]
Message-ID: <1043388556.12894.23.camel@localhost> (raw)
In-Reply-To: <310350000.1043367864@titus>
On Thu, 2003-01-23 at 18:24, Martin J. Bligh wrote:
> > I've heard some say that O(1) sched can only really help on systems with
> > lots and lots of processes.
> >
> > But my systems run about 600 processes max, but are P4 Xeons with HT,
> > and we kick off several hundred processes sometimes. (sleeping to
> > running then back) based on things happening in the system.
> >
> > I am possibly going to forgo putting O(1)sched in production *right now*
> > until I've got my patch solid. But I got to thinking, do I need it at
> > all on a Oracle VLDB?
> >
> > I think yes, but I wanted to get some opinions/facts before making that
> > choice to go without O(1) sched.
>
> How many *processors*? Real ones.
>
> M.
>
Quad P4 Xeon. Dell 6650
next prev parent reply other threads:[~2003-01-24 6:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 0:10 Using O(1) scheduler with 600 processes Austin Gonyou
2003-01-24 0:24 ` Martin J. Bligh
2003-01-24 6:09 ` GrandMasterLee [this message]
2003-01-24 6:18 ` Martin J. Bligh
2003-01-24 6:27 ` GrandMasterLee
2003-01-24 6:48 ` Martin J. Bligh
2003-01-24 8:50 ` William Lee Irwin III
2003-01-24 2:05 ` mgross
2003-01-24 6:08 ` GrandMasterLee
2003-01-24 18:22 ` mgross
2003-01-24 21:44 ` GrandMasterLee
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 0:24 Perez-Gonzalez, Inaky
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=1043388556.12894.23.camel@localhost \
--to=masterlee@digitalroadkill.net \
--cc=austin@coremetrics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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