From owner-freebsd-questions Sat Feb 10 7:37:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 154E237B65D for ; Sat, 10 Feb 2001 07:37:30 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA21077; Sat, 10 Feb 2001 10:37:28 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA21570; Sat, 10 Feb 2001 10:37:27 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA21566; Sat, 10 Feb 2001 10:37:27 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sat, 10 Feb 2001 10:37:27 -0500 (EST) From: Kenneth Wayne Culver To: janne Cc: questions@FreeBSD.ORG Subject: Re: how much ram can 3.4 handle In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > we uppgraded hardware from p166 250mb ram to p3 800 1000 mb ram, and > now we have problem when we run our application it eats all memory > after approx 10our and display it as inactive (when we use "top").Then > the hardware totaly crasch.Can 3.4 handle that 1G ram memory. 3.4 can handle that kind of memory as far as I know, because for a while I think ftp.freebsd.org/ftp.cdrom.com were running 3.x with 2 or 4GB of ram. If you're getting crashes, first I would suspect bad ram. Also, the "inactive" memory thing is normal. It is what's "supposed" to happen. That just means that the ram marked inactive hasn't been marked "free" yet, but isn't currently being used by any programs. That memory can still be used for other programs, and some memory monitors for my windowmanager even consider "inactive" as being unused. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message