Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: John Ames <commodorejohn@gmail.com>
Newsgroups: comp.lang.forth
Subject: Re: Memory trashing? Virtual memory question.
Date: Mon, 30 Sep 2024 07:54:14 -0700
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <20240930075414.000029ba@gmail.com>
References: <nnd$0b021237$626a8881@55133cc8c31c4c51>
	<nnd$56a65fea$30328e9e@fe5292c2aea63e4d>
	<f9e2a709183796c9cee0d60d24b0cf89@www.novabbs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 30 Sep 2024 16:54:19 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="32a37bac0a08e2ecfa3e3c65131391e5";
	logging-data="2208221"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/1iPtP/elwCPHhhrlglM+Wb0Woor+IhD0="
Cancel-Lock: sha1:zuGIvUJ0DLo4vJliFHsec5R/Kgs=
X-Newsreader: Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
Bytes: 1778

On Mon, 30 Sep 2024 07:26:23 +0000
mhx@iae.nl (mhx) wrote:

> I hoped to  improve matters with the Working-Set size (which is
> explicitly shown on Windows 11's Task manager) but was not successful
> at the time (will look again).

(Not directly relevant to the problem, but just for the record: Task
Manager's memory-usage reports in newer versions of Windows - 10/11 for
sure, I think 8 as well - are blatant lies, which I'm about 90% sure
was deliberate obfuscation on MS's part to downplay the extent to which
OS memory hogging spiked in those versions. Resource Monitor gives a
considerably more accurate picture of where everything is going, though
even then the numbers don't always tally up.)