From owner-freebsd-isp Wed Sep 18 14: 8:32 2002 Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9194737B401 for ; Wed, 18 Sep 2002 14:08:31 -0700 (PDT) Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1394F43E6A for ; Wed, 18 Sep 2002 14:08:31 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [210.49.77.192] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5324aadf) with ESMTP id tomhaaaa for ; Thu, 19 Sep 2002 07:08:55 +1000 Message-ID: <3D88EB35.7080303@quake.com.au> Date: Thu, 19 Sep 2002 07:08:05 +1000 From: Kal Torak Organization: Quake Networking User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9) Gecko/20020311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pzw@aabc.dk Cc: isp@freebsd.org Subject: Re: SV: Inactive memory in FreeBSD References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org pzw@aabc.dk wrote: > While this is a fine and dandy idea, I have experienced a serious downgrade > in response time for some of my websites, when the system has converted all > free memory to inactive memory. After a reboot, there was no problem with > response time. This has nothing to do with the amount of inactive memory, this would be the result of a program leaking or consuming large amounts of resorces that it didnt need.. Have a look at the memory usage of your programs when they are first started and then compare that to the usage of when you notice the downgrade.. You will probably find something is using huge amounts of memory.. Thats a bug in the program most likely and you should report it or upgrade to a newer version or switch to a different program that does the same thing.. If you MUST use that software you could set a cron job to kill the process and start it again every few days or whatever you think is needed so that memory is released... Unlike windows you dont need to reboot to salvage leaked memory! > I've read the article about the VM design, and it is like you say, but, the > overhead on memory allocation from inactive memory, instead of free memory, > must be very high, that's the only way to explain the situation above. Inactive memory is not a bad thing! Where do you get this idea that free memory is better than inactive?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message