Ulterius
Incorrect amount of ram showing up
Uuuhhh... alright. I'll have to go over this one with Andrew, I think.
Windows now has a feature for memory compression.
In Windows 10, we enabled the Memory Manager (MM) to compress infrequently-accessed memory pages which reduces the amount of reads and writes to the disk (pagefile) and therefore improves responsiveness. By compressing memory we reduce the amount of memory used per process, allowing the operating system to maintain more applications in physical memory at a time before enacting traditional paging.
When Memory Manager’s policy does dictate paging, the data being written to or read from the disk is already compressed to typically around 40 percent of its original size. This compression improves the performance of other unrelated operations on the system by reducing a major source of interfering IO load. The end result is a snappier, more responsive experience with improved app launch performance and consistency.
I believe this is why we are seeing a a higher value. We need to read the value for 'used' in a different way. I'll have to check but either it can be read directly or we can subtract the amount saved with compression.
On further analysis it seems the problem is in how to conversion is done. Changing the bytesToSize function now reports 15.88GB which I suspect is less than system memory due to hardware reserving some address space. It may also relate to issue #12 . Fixed code as follows:
export function bytesToSize(bytes){
if (bytes >= 1099511627776) {bytes=(bytes/1099511627776).toFixed(2)+' TB';}
else if (bytes>=1073741824) {bytes=(bytes/1073741824).toFixed(2)+' GB';}
else if (bytes>=1048576) {bytes=(bytes/1048576).toFixed(2)+' MB';}
else if (bytes>=1024) {bytes=(bytes/1024).toFixed(2)+' KB';}
else if (bytes>1) {bytes=bytes+' bytes';}
else if (bytes==1) {bytes=bytes+' byte';}
else {bytes='0 bytes';}
return bytes;
}
The performance monitor reports 123 MB as being hardware reserved, confirming my suspicion of the missing memory.