Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Joe Buehler Subject: Re: procps and top output Date: Wed, 30 Apr 2003 13:00:33 -0400 Organization: Spirent Communications, Inc. Lines: 21 Message-ID: <3EB00131.8090209@hekimian.com> References: Reply-To: jbuehler@hekimian.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en In-Reply-To: X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Chris January wrote: >>It's the output of "top", and yes, I see the problem too. The "size" >>column is always around 400 (+/-) MB, however large or small the process. >> >>The RSS size is correct - it matches the resident set size in the >>Windows task manager process display. It's only the "size" (== "VM size" >>in task manager?) that seems to be off. > > I noticed this when I was porting procps but I never had time to investigate > exactly why this is so. It might be because VM size also includes DLLs and > file mappings. I just noticed something that might be related to this (old) post. Cygwin reserves 400 MB of virtual memory, I assume for the heap. It commits only a little. So the large sizes shown by (e.g.) "top" are probably because they are memory that is "reserved", while memory that is "committed" is probably what is really wanted. -- Joe Buehler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/