Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: "cygwin" <cygwin AT cygwin DOT com>, "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Subject: RE: [avail for test] libtool-devel-20030121-1
Date: Fri, 7 Feb 2003 11:30:48 +0100
Message-ID: <000701c2ce93$faaa89f0$0a1c440a@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <3E420A43.8010709@ece.gatech.edu>

> You never followed up on that.

Rebooting every time need very much time (about 10 minutes for me) and there is
an easier way to emulate that. I've written an applications which's allocate any
available memory. This removes all cached files' dll's and so one. I had similar
problems while inspecting the kde loading time and have read this tips somewhere
in the internet.

See http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/kde-cygwin/tools/fillmem/ for
further informations.

See in the task manager how many virtual memory you have and call fillmem with a
value near this limit (in Bytes).

PS: Does anyone have an idea, how to get the available virtual memory through an
api function ?

Ralf


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/