From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 9 03:14:29 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B9B916A420 for ; Fri, 9 Nov 2007 03:14:29 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: from outgoing16.3gate.net (outgoing16.3gate.net [202.127.97.16]) by mx1.freebsd.org (Postfix) with SMTP id CE4BE13C4AA for ; Fri, 9 Nov 2007 03:14:26 +0000 (UTC) (envelope-from binto@triplegate.net.id) Received: (qmail 70767 invoked by uid 1011); 9 Nov 2007 03:08:36 -0000 Received: from 202.127.97.100 by mx2.3gate.net (envelope-from , uid 1009) with qmail-scanner-1.25-st-qms (clamdscan: 0.86.2/1034. spamassassin: 3.0.2. perlscan: 1.25-st-qms. Clear:RC:1(202.127.97.100):. Processed in 0.042917 secs); 09 Nov 2007 03:08:36 -0000 X-Antivirus-3GATE-NET-Mail-From: binto@triplegate.net.id via mx2.3gate.net X-Antivirus-3GATE-NET: 1.25-st-qms (Clear:RC:1(202.127.97.100):. Processed in 0.042917 secs Process 70761) Received: from smtp.triplegate.net.id (HELO lb1.3gate.net) (202.127.97.100) by outgoing16.3gate.net with SMTP; 9 Nov 2007 03:08:36 -0000 Received: from webmail.triplegate.net.id (unknown [202.127.97.10]) by lb1.3gate.net (Postfix) with ESMTP id 93A7C211046; Fri, 9 Nov 2007 10:11:35 +0700 (WIT) Received: from 202.127.98.144 (SquirrelMail authenticated user binto@triplegate.net.id) by webmail.triplegate.net.id with HTTP; Fri, 9 Nov 2007 10:19:14 +0700 (WIT) Message-ID: <1318.202.127.98.144.1194578354.squirrel@webmail.triplegate.net.id> In-Reply-To: <54da514e0711081429g5535598exef08cb46765fa591@mail.gmail.com> References: <4635.202.127.98.144.1194407276.squirrel@webmail.triplegate.net.id> <54da514e0711071023g565cf98ay54ff2bb9cfeeb38a@mail.gmail.com> <28483.202.123.224.34.1194493720.squirrel@webmail.triplegate.net.id> <54da514e0711081429g5535598exef08cb46765fa591@mail.gmail.com> Date: Fri, 9 Nov 2007 10:19:14 +0700 (WIT) From: "binto" To: "Doug Clements" User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: binto , freebsd-hackers@freebsd.org Subject: Re: page fault & degaradation performance X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2007 03:14:29 -0000 Btw, what is page replacement algorithm that used by FreeBSD...sorry I'm newbie..LRU or another algorithm? > Running out of memory and having to continually swap things in and out > of ram degrades performance, yes. Page faults are simply how the > virtual memory subsystem gets things done, like pulling things out of > swap. > > --Doug > > On Nov 7, 2007 7:48 PM, binto wrote: >> Btw >> >> Even page fault isn't a terrible thing, but she could make >> trashing condition..that can degrade CPU utilization, am i correct? >> >> >> >> >> >> >> > On 11/6/07, binto wrote: >> >> >> >> I just wanna know, >> >> how to reduce the number of page faults to upgrade program or OS >> >> performance? >> >> is there any parameters that i must set if i reduce the number of >> page >> >> fault? >> > >> > >> > Don't forget that some amount of page faults are normal consequences >> of >> > using a machine with virtual memory. Page faults alone are not an >> > indicator >> > that you're out of memory or suffering in any way, they just mean that >> > something was requested in vm that wasn't actually in ram, and needed >> to >> > be >> > loaded. Ask 'swapinfo' or 'top' to see if you might possibly benefit >> from >> > more ram by reducing paging. >> > >> > --Doug >> >> > _______________________________________________ >> > freebsd-hackers@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> > To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" >> > >> >> >> >