[Autogenerated] Let's see if you can find these various lists in some tools.
Let's start with task manager.
So with task manager you can see this memory composition part here.
So in fact the memory composition provides some hint as to these
paging list that we've seen in the previous video.
So first, if I hover over this location,
we can see the amount of memory which is currently in use in use means
that this is part of working set of processes or the system that's this
5.3GB which is currently used in Iran.
So this is part of working set of processes and the
system then notice this little piece here.
That's the modified page list.
These are all the pages that are currently in physical memory that have not
been yet synchronized or written to their proper location.
The page file.
So you see that this is a relatively small amount of memory or small
number of pages and then the rest of this almost all of it.
It's standby.
So in fact, most of the memory here is standby.
That's like 10.6GB.
In fact, that's what available here is trying to convey.
Well, it's actually part of that available thing.
The last piece here, as you can see here,
that's the free page list,
but it's not really the free page list only it actually
consists of the zero page and the free page.
Both of them are marked here as free task measure doesn't provide the
distinction and that makes sense in the sense that both of them are
available for processes and the system to use.
So task measure provides some hints to be more precise.
We can use Process Explorer with Process Explorer can go to view system
information to see some information about the system.
So you have a summary here indicating stuff about CPU consumption,
commit size and other stuff.
We can go to memory to get some more details here and here.
You can find the various list,
you can see the zero page list is 100 and 62 something
1000 kilobytes or 162 megabytes roughly notice the free
page size which is very small,
which just shows you that the free page list is a very small one.
And normally it grows when the process terminates with all
its private memory going to be free.
And then the zero page thread or threats wake up and they
will zero out that memory fairly quickly.
So for example, I have visual studio.
If I try to close that, let's see if we can see something useful here.
You notice free page sizes has grown and then they immediately start to
dwindle down very quickly because the zero page thread took all that private
pages which Visual Studio visual studio and then made them 00 00 notice zero
page count here has increased significantly.
Here's the modified page size that the 66 MPS or
something we've seen in task manager.
The most interesting part here perhaps is the standby
page list and the standby page list.
In fact it's not a single list.
This is eight lists.
They have these priorities.
Because the real question is when you have a page in the standby
page list and now the system decides that it has to take a page
and throw that to the free page list because system starts to run
out of physical memory.
And the question is which page should that be?
Perhaps the most logical thing to do is to grab a page,
which is the father's one in time.
That in terms of usage and it makes sense however,
perhaps it's not ideal because in some cases you might have
processes that are more important than others.
And this is reflected by this property called memory priority.
And so what you see in these priorities indicate which
pages are more important than others.
Priority zero is the least important pages and priority
seven is the most important pages.
So for example, we have a background process that is running background mode.
You might recall background mode from the threats course.
So if we right click here, we can go to set priorities.
Set background mode.
When you set the background mode for a process or a process
voluntarily put itself into background mode,
the mental priority drops to one.
The default by the way is five.
So five is the default.
That's why you see most of the pages are in priority five,
which means that when the page is needed,
priorities zero is going to be emptied first and then priority one,
then priority two and so on.
So they hide the priority.
The more likely these pages will remain physical memory.
So the next time page fault occurs is going to be a soft painful for
these pages and going to bring them back to the processing question
without having to incur any kind of I O So priority five is the
default and for background processes, priority one is being used,
you might be wondering why it's priority six or seven here,
what are they used for?
So these are used for the pre fetch or the prefix
service or super fetch service.
And so the super service purpose is to bring data and code into
ran before you need it to be more precise.
And so the idea here is that if for example the system,
the super fetch service really tracks your usage of the system,
it knows that you're using Notepad almost all the time.
Whenever you research the system is going to load note pads,
initial pages at the very least immediately.
So they're available whenever you actually try to launch
Notepad to launch very quickly quicker than in the case
where these weren't already there.
And so these pages have the highest possible priority because you
might want them to remain in physical memory for as long as possible
because these are pages you're using a lot,
that's at least the assumption from the super fridge service perspective.
So here we can see the size of these various lists understand
by you can see it's not really that simple as you might have
got from the previous video.