Date: Wed, 18 Sep 2002 15:19:43 +0200 From: pzw@aabc.dk To: gldisater@gldis.ca Cc: isp@freebsd.org Subject: SV: Inactive memory in FreeBSD Message-ID: <E01A200E2339D311AF7E00508B319A2B04C84713@expers.aabc.dk>
next in thread | raw e-mail | index | archive | help
Well, yes, it might be a good thing when you have a lot of reoccurring tasks, and plenty of memory. However, when you compile a program or FTP a file to the server, the chances of you doing that over and over again is almost null, therefore caching these processes are a total waste. So, FreeBSD is best used for a server system, where you have more RAM than you use for all normal activity, and to prevent some seldom used tasks to hog up memory, you should reboot often. As a workstation system, you're better of using Windows or Linux, unless ofc. You're a secretary using the same word processor program day in and day out. IMHO it would be a far better solution, for you to be able to specify the maximum amount of memory that a program could hog up, so you don't have to reboot all the time to free memory. Best Regards, Peter >This is how the vm subsystem is supposed to work. This is normal, this >is good. Inactive memory is memory that currently has data (programs) >stored in it, but that data is not currently being used (the programs >are not currently running). If the data that is currently stored in the >inactive memory is needed again (you run a program again), you don't have >to load it off the hard drive. >This is a good thing. You don't want to change this. >The comparison to solaris is irrelevant, as they (solaris and FreeBSD) have >different vm subsystems. >-- >Jeremy Faulkner http://www.gldis.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E01A200E2339D311AF7E00508B319A2B04C84713>