From owner-freebsd-hackers Tue Mar 10 18:00:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24841 for freebsd-hackers-outgoing; Tue, 10 Mar 1998 18:00:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24830 for ; Tue, 10 Mar 1998 18:00:30 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id VAA06441; Tue, 10 Mar 1998 21:12:02 -0500 (EST) (envelope-from mark) Message-ID: <19980310211202.06813@vmunix.com> Date: Tue, 10 Mar 1998 21:12:02 -0500 From: Mark Mayo To: hackers@FreeBSD.ORG Subject: Context switches on cdrom.com ?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm just curious what the context switches per second numbers are like on a busy machine like ftp.cdrom.com.. What are people seeing on heavily loaded machines (where, in this case, heavy load means tons of processes)? I'd like to plop a FreeBSD machine into an installation that sees a lot of mail, and typically has about 700-1000 processes running. On my low-load servers around the house and lab, I rarely see the Csw number go above 250-300, but I only have about 150-200 processes.. I have managed to push Csw past 1000 on my PPro at home, but artificial tests like that rarely have anything to do with the Real World(tm)! :-) TIA, -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message