Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<42AE11C6.2B560356@dessent.net>
Date:	Mon, 13 Jun 2005 16:07:50 -0700
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: question: high virtual memory usage
References:	<200506132245 DOT j5DMjhYm063267 AT relay1 DOT wplus DOT net>
X-Spam-Report:	-5.7/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.2 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Alexey Fayans wrote:

> Look at screenshot:
> http://home.shad.pp.ru/tmp/cygwin.png

You're using process explorer, not task manager, and process explorer
does not interact well with Cygwin for whatever reason.  In this case it
seems the procexp is computing the VM size wrong.  If you use task
manager and look at the "VM size" column it will be correct.  You'll
have to take this up with sysinternals.com, it's not on topic for this
list.

The "VM size" column is not a good measure of the actual memory used. 
It does not correlate in any way to real memory, hence virtual.  You
should consider the "working set" column if you want to know how much
memory a process is actually using.

Brian

--
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/

- Raw text -