I have very often noticed that during times of reduced responsiveness my CPU is burning cycles doing memory compression like so: In short: If I didn't compress, by my understanding my memory requirements would be 15388-6855+16657 = 25190 MB. If uncompressed, this would use 16657 MB. Just to summarise the pertinent points from that screenshot: For example, when opening a particular model I experience this: Since the anniversary update I have experienced significant performance issues with my machine, and while investigating I noticed that windows appears to be fairly aggressively compressing memory. Historically my worksets have occupied anywhere from 4-30 gb of RAM. Perhaps not memory hungry in a 8tb supercomputer sense, but memory hungry in the 'more than word/email/youtube and even chrome' sense. I do a lot of scientific/engineering computing simulation with bespoke and memory hungry applications. I am wanting to know why Windows is choosing to compress my memory (and hence use CPU cycles and render my system slow and unresponsive) when my system appears to have sufficient memory to store the entire application footprint in memory uncompressed.) I thought the reason would be obvious from reading the two questions but to summarise: I don't have a memory leak. (EDIT: I have been asked to explain why my question is not a duplicate of this question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |