Re: Gradual Growth of Memory Use?
"David McClain (as dbm at refined-audiometrics dot com)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
Max analysis duration now showing 36 ms, down from 450 ms. Most durations are 5 ms, versus 150 ms. So waterfall display has a huge impact on processor use. > On Mar 15, 2025, at 05:39, David McClain <[email protected]> wrote: > > I am running another data acquisition, this time with the waterfall image display disabled. Memory use by LWW still grows, but more slowly. Explorer memory use not significantly growing after only 15 minutes. I’ll check back in a few hours. > >> On Mar 15, 2025, at 05:24, David McClain (as dbm at refined-audiometrics dot com) <[email protected]> wrote: >> >> Okay… Finally have more than 24 hours of non-stop data acquisition. >> >> Conditions: >> Telemetry data saved to prealloc arrays - so no growth, just fill-in >> Full running graphic displays >> Stop after 33 hours of data acquisition - only one buffer-fill fault shown, around hour 27, max analysis time 450 ms >> Memory use at start was 130 MB, growing to over 2 GB at finish. >> >> I still cannot account for massive memory growth, but I suspect that it has to do with the running graphic display of a synthesized image (waterfall display). >> >> The overall memory use grows from 4 GB to over 9 GB, with no compressed memory showing. But the “hog” in the memory is Explorer.exe (!), at over 7 GB. I am not overtly running any instances of Explorer. >> >> When I reboot the system and begin anew, the monitor shows that Explorer.exe is launched just after I launch LWW. LWW PID = 7028, Explorer PID = 7048. At start, we have LWW memory at 130 MB, and Explorer at 110 MB. I did not invoke explorer.exe, but maybe the CAPI graphics system does this? >> >> >>> On Mar 14, 2025, at 23:04, Dmitry Ivanov (as ystok-systema at mail dot ru) <[email protected]> wrote: >>> >>> Hello folks, >>> >>>> Have a look at this article: >>>> https://bardimin.com/en/windows-en/tips-and-tricks/easy-ways-to-enable-and-disable-memory-compression-to-improve-windows-11-performance/ >>> >>> I have tested on Windows 10. >>> >>> PS> Disable-MMAgent -mc >>> >>> Reboot >>> >>> PS> Get-MMAgent >>> >>> ApplicationLaunchPrefetching : True >>> ApplicationPreLaunch : True >>> MaxOperationAPIFiles : 256 >>> MemoryCompression : False >>> OperationAPI : True >>> PageCombining : True >>> PSComputerName : >>> >>> Nevetheless, I see in the Task managaer: >>> compressed 200 MB >>> available 1.5 GB >>> >>> -- >>> Dmitry Ivanov >>> lisp.ystok.ru >>> >>> _______________________________________________ >>> Lisp Hug - the mailing list for LispWorks users >>> [email protected] >>> http://www.lispworks.com/support/lisp-hug.html >> >> >> _______________________________________________ >> Lisp Hug - the mailing list for LispWorks users >> [email protected] >> http://www.lispworks.com/support/lisp-hug.html > _______________________________________________ Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html