[Autogenerated] let's examine process Explorer now.
So here's the column private bytes private bytes is shown by default and
private bytes in process Explorer is exactly the same as commit size in
task manager and it is unfortunate that the names are different but the
fact that means exactly the same thing, you can definitely make that comparison.
Here's task manager.
Just to just to prove that here's the commit size for Visual Studio here,
you can see it's exactly the same value as shown here
for Visual Studio in process Explorer.
So this is exactly the same thing you can see here,
another column which is the working set notice there's no private or
anything before that meaning this is the full working set of the process
essentially all the physical memory currently being used by the process
notice this is just the private memories,
not the full committed memory in the process.
If we rightly can go to select columns,
there's a tab here called process memory which provides all the
counters you can think in relation to memory.
So here's where you can add something like maybe shared,
commit or virtual science or virtual size.
One of those counters I mentioned earlier that indicates the entire
usage of address space in the process for pages which are reserved
and committed so essentially or committed.
So not free pages and you see that many of these processes have this large
sizes here and you might remember from the previous model,
this is due to the C F G beaten up the control flow guard beat map,
there's a large chunk chunk of reserved memory there.
You notice the committed size is much much smaller.
So obviously most of that memory indicating here is
actually reserved and like I said,
we'll discuss what C f G is in the last module in the scores Anyway,
we can go back to select columns and go to process memory.
You can see here all the various aspects of the working set.
So this is the current working set,
we can go with the working set for private memory only,
just like in task manager and there's also a maximum working set.
You can even get a private delta bytes here,
which shows a nice graph of how memory is being changed through time.
Well actually it's not a graph here,
it's just the delta showing you the changes in memory consumption
for processes every time process Explorer is updating which is by
default every second there's actually a private bite history here
which does show the graph.
So it's possible to see the graph here indicating the usage of private
bytes in corresponding to time because you might lose the particular
counter if you're not looking close enough.
But if you want to see some progress as to how the
process uses its private memory,
you can use this graph to give you a nice sense of how these things work.
So for example,
in Visual Studio let me go back to process Explorer and make it uh well,
let's first open something so we can perhaps open some project here.
Doesn't matter which project that is.
The point is to consume more memory.
And you'll see that the memory consumption has increased in visual
studio so you can see more private bytes are being used now and is
easily discerned here using the graph, not just a number you can look at,
but also seeing that in graphical form,
which could be very useful if you're trying to investigate something and
see what's going on in terms of memory consumption.