I would like to be assured that the author knows the difference between actual memory and setting aside paging space.

tredre3 28 minutes ago | parent | next [-]

The author doesn't need to know the difference because the task manager is accurate by default. I can still offer you some reassurance:

- The Windows task manager's memory column is the private working set which is the actual memory used by the application minus shared memory (but only shared memory that is currently shared with other processes, not merely marked shared. I.E. it's similar to RES - SHR on Linux but it's more accurate)

- Windows doesn't overcommit memory. Memory that is reserved but unused (not touching all pages) by the app is truly wasted. I mention this because in your other comment you make it clear that you think this is happening. But Windows isn't Linux.

▲

benj111 2 hours ago | parent | prev [-]

That still isn't a good look.

	▲	hyperhello an hour ago \| parent [-]
		I’m not sure if you mean a good look for the process or for the author but paging space is just saying “gimme a gigabyte” like saying “gimme a plate” is at a barbecue. The resources themselves aren’t being used at that point.