Windows Defender really SUCKS, eating up unreasonable amount of HDD res
|
|
 Jun 16 2017, 12:24 PM
Return to original view | Post
#1
|
 
Senior Member
3,038 posts Joined: Nov 2009 
|
the allocated virtual ram is not 4gb. from screenshot it's 2. running w10 with 2gb ram might trigger swap use more often, causing 100% cpu usage also.
i run w10pro on virtualbox. (4gb ram; 40gb hdd) i only have brief moments of high ram usage sometimes, not always. |
|
|
|
|
|
Jun 16 2017, 03:45 PM
Return to original view | Post
#2
|
|
Senior Member
3,038 posts Joined: Nov 2009
|
QUOTE(CKKwan @ Jun 16 2017, 02:40 PM) The Allocated RAM is 4GB. Hyper-V will dynamically increase / decrease the RAM available. dynamically allocated ram is a nice feature in hyper-v in theory, but sometimes it doesn't work as expected. in general, a w10 vm with static 2gb runs better than a vm with 4gb dynamic ram in hyper-v. (just try it out if you want)Besides, there isn't any software running at the moment. Only Windows Defender was running at the background.  however, i agree that windows defender is the most common app that causes full disk usage (especially if the os/vm is on hdd). for relatively optimal use, run vm on ssd, and do some manual tweaks to it. This post has been edited by horns: Jun 16 2017, 03:49 PM |
|
|
Jun 16 2017, 04:29 PM
Return to original view | Post
#3
|
|
Senior Member
3,038 posts Joined: Nov 2009
|
QUOTE(CKKwan @ Jun 16 2017, 04:19 PM) But in this case, I do not think that the high HDD usage is caused by the dynamically allocated RAM. maybe; but it contributes to overall sluggishness due to much lower iops. looking at that high cpu usage, i suspect swap file on hdd was in action. |
|
|
Jun 16 2017, 07:03 PM
Return to original view | Post
#4
|
|
Senior Member
3,038 posts Joined: Nov 2009
|
QUOTE(CKKwan @ Jun 16 2017, 05:48 PM) Besides dynamically allocation of Memory, Hyper-V also dynamically scale back the CPU time allocated to the VM. That is why a lot of time you will notice CPU usage is very high. er what you said are ok, in general, on paper. problems lie in behaviors of hyper-v during actual applications. maybe dig a little deeper on common issues and best practices of hyper-v.Windows Defender shouldn't use so much memory that it causes the OS to start swapping into HDD. When memory is not sufficient, Hyper-V should first allocate more from the host (until its limit is hit) before telling the OS that there is no sufficient memory and triggered a swap. Besides, Windows Defender is (the only) actively running, if the OS wish to swap some thing out of memory, it should have swap something (which is idle) else instead of Windows Defender. i understand that your main point is about how bad windows defender is. however i run w10pro vms for some times now (virtualbox and hyper-v; fixed 4gb ram; 4 cpu vcores). windows defender doesn't give me high cpu/disk/mem issues so far. |
|
|
Jun 16 2017, 07:23 PM
Return to original view | Post
#5
|
|
Senior Member
3,038 posts Joined: Nov 2009
|
QUOTE(CKKwan @ Jun 16 2017, 07:09 PM) The theory (deep inside) will basically affect all applications running inside hyper-v. Which is a MORE serious problem than just Windows Defender alone. the thing is that i don't have such a problem If whatever you said is true, then you should have noticed that your VM is behaving unexpectedly.  |
|
|
Jun 16 2017, 08:08 PM
Return to original view | Post
#6
|
|
Senior Member
3,038 posts Joined: Nov 2009
|
QUOTE(CKKwan @ Jun 16 2017, 07:26 PM) That is fine, I only disagree with your weird theory ok and sorry for annoying you with my 'weird' theories. just ignore them all. |
| Change to: |  0.0167sec
 0.96
 7 queries
 GZIP Disabled
Time is now: 12th December 2025 - 02:35 PM |
Quote