Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-11 > #18465
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Newsgroups | alt.comp.os.windows-11 |
| Subject | Re: memory usage vs fan usage |
| Date | 2025-04-17 19:57 +0100 |
| Message-ID | <m6d183Fcl4lU3@mid.individual.net> (permalink) |
| References | <m6cgr0Fa4thU1@mid.individual.net> <vtr93h$10brs$1@dont-email.me> |
Paul wrote: > Andy Burns wrote: >>> I've always been a bit suspicious of the MemoryCompression >> service, so I'm experimenting with it turned off for a bit. >> (powershell disable-mmagent -mc) > > Makes sense, but the first question you have to ask, is why > the Memory Compressor is sucking cycles, on machines which > are not down to their last byte of memory. > > On W10, between 250MB in use all the way up to 1GB in use, > the compressor goes from "railed" at the how end, to barely > doing anything at all on a machine equipped with 1GB of RAM. > I did some tests in a VM, to see how it behaves. This was > back when the Memory Compressor was visible in Task Manager. > > You have 16GB or 32GB, and the Memory Compressor should be > taking a snooze in such a case. Is that its defined behaviour, or just what a normal person would hope it does? > Only when the memory use is > at 90-95%, should the compressor be picking up again. > > On Linux, something called "swappiness" defines some of > the memory management behavior. Linux distros, some of > them start to swap at half full, others allow the OS > to get within 50MB of exhaustion, before doing > something about it. Does Windows perhaps have a similar > policy ? Yes, I'm aware of that "dial" > I used Process Explorer to watch the Memory Compressor, then > ran my malloc64.exe test program (home-brew code), and the > Memory Compressor only started to consume cycles near the > very end of the run. There was no sign of any changed > behavior that would account for your memory compressor > to be running. When you're down to 250MB of memory left, > you should start to see a response. I know it doesn't fully hide from taskmgr or procexp, but why does it have to hide what it's doing from them? I mean it must have a .exe or .dll somewhere, how much CPU usage does it do behind a curtain?
Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-17 15:16 +0100
Re: memory usage vs fan usage Paul <nospam@needed.invalid> - 2025-04-17 12:09 -0400
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-17 19:57 +0100
Re: memory usage vs fan usage Paul <nospam@needed.invalid> - 2025-04-18 03:15 -0400
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-17 11:59 -0500
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-17 19:40 +0100
Re: memory usage vs fan usage Frank Slootweg <this@ddress.is.invalid> - 2025-04-19 12:04 +0000
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-19 13:36 +0100
Re: memory usage vs fan usage Paul <nospam@needed.invalid> - 2025-04-19 09:25 -0400
Re: memory usage vs fan usage Frank Slootweg <this@ddress.is.invalid> - 2025-04-19 14:54 +0000
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-19 16:16 +0100
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-24 08:17 +0100
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-24 05:14 -0500
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-24 11:30 +0100
Re: memory usage vs fan usage Paul <nospam@needed.invalid> - 2025-04-24 09:08 -0400
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-24 20:59 -0500
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-25 07:40 +0100
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-25 19:13 +0100
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-25 22:29 -0500
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-26 10:31 +0100
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-26 15:05 -0500
Re: memory usage vs fan usage "Carlos E.R." <robin_listas@es.invalid> - 2025-04-19 14:36 +0200
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-19 13:56 +0100
Re: memory usage vs fan usage Paul <nospam@needed.invalid> - 2025-04-19 09:28 -0400
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-17 15:07 -0500
Re: memory usage vs fan usage "Carlos E.R." <robin_listas@es.invalid> - 2025-04-17 22:25 +0200
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-17 19:30 -0500
Re: memory usage vs fan usage "Carlos E.R." <robin_listas@es.invalid> - 2025-04-18 14:09 +0200
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-18 11:13 -0500
Re: memory usage vs fan usage "Carlos E.R." <robin_listas@es.invalid> - 2025-04-18 21:33 +0200
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-17 22:12 +0100
Re: memory usage vs fan usage VanguardLH <V@nguard.LH> - 2025-04-17 20:07 -0500
Re: memory usage vs fan usage Paul <nospam@needed.invalid> - 2025-04-18 05:24 -0400
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-18 12:08 +0100
Re: memory usage vs fan usage Frank Slootweg <this@ddress.is.invalid> - 2025-04-18 18:09 +0000
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-18 19:36 +0100
Re: memory usage vs fan usage "Carlos E.R." <robin_listas@es.invalid> - 2025-04-17 22:29 +0200
Re: memory usage vs fan usage Andy Burns <usenet@andyburns.uk> - 2025-04-17 22:17 +0100
Re: memory usage vs fan usage "Carlos E.R." <robin_listas@es.invalid> - 2025-04-18 02:19 +0200
Re: memory usage vs fan usage Paul <nospam@needed.invalid> - 2025-04-18 05:52 -0400
csiph-web