[Autogenerated] the most common question about page files
is what should their size be in fact, is the system managed option,
Windows a good one.
So in the old days, the default page size was based on the size of RAM.
In fact the values weren't very helpful.
The initial size was set to one times RAM and the maximum size was set
to three times RAM if you use page file managed.
So they managed options so that you don't have to worry about that.
If you think about it, that doesn't make much sense.
The size of RAM has nothing to do with your memory utilization.
In fact, it might be contrary to in some cases,
for example, suppose you're, you're buying 64 gigabytes of frame,
you're buying lots of framing so you don't have to
rely on the page file so much,
but you get 64 gigabyte as the initial size of of the page file,
which doesn't make much sense and perhaps still valuable SSD drive size from
your Docker And so Windows eight made things slightly better by capping the
system managed case for the maximum size to 32GB.
But still, that doesn't make enough sense.
And in fact,
it forced people that are aware of that to make sure that their initial
maximum size is set in the way that makes sense for their system and spend
a little bit more about that in the next demo.
But Windows 10 in general make things good again and the basic idea there was,
is to track the usage of committed memory by the user for a period of two
weeks to get a sense of what's going on there and then tweak the page file
size accordingly based on what is actually being used,
the actual workload used by that user.
This makes much more sense than trying to figure out the size based on RAM.
It has really nothing to do with RAM.
It has to do with how the user is using the system,
what the memory consumption on average, perhaps.
How can we make the page file accommodate that so that
the user doesn't run out of memory.
So let's see what that looks like when we examine task manager.