[Autogenerated] let's open task manager here,
if I go to the performance tab and go to memory we can see
what's going on in terms of memory here.
So first notice the commit size,
the commit size is 5.4 gigabytes right now with all the stuff I have opening on
this system and after the slash we have the commit limit.
The commit limit is really the size of RAM plus the current size of
the page file you might recall from the previous demo that the page
file size is roughly 2.4 gigabytes.
And so it makes sense as RAM here is configured to be 16 gigabytes,
so we have 80.4 gigabytes of memory, we can commit.
So we have 5.4 at this point we can commit up until 18.4.
And so the question is, what should the page file size really be?
And the answer is it depends on how I work with my system.
So for example,
if 5.4 is in fact my normal way of working that perhaps the
average that I need for my normal work,
that in fact I don't need a page file at all because I
have everything that I need using Ram, I don't need more storage.
If for example, my committed size was on average 20 gigabytes, let's say.
And I have a system with 16 gigabytes of RAM.
Then the page five size I need is four gigabytes.
That would be usually the initial size and probably do the maximum
size slightly higher to make sure that even if I have some peaks in
my work and I might need some more memory occasionally I would be
able to get it and so the proper size of the page file shouldn't
really depend on ramp at all.
In some kind of formula it should depend on RAM but based on the actual
workload I have and I'm using my system for so for this particular example
here I don't really need any page file at all.
However,
having a page file even in this case is beneficial for a different reason.
If you get a blue screen on your system,
you might want to get a dump files that you can then analyze.
The reason for the blue screen now dump files and not really
directly to the file that is configured here.
If you go to system properties for a moment,
there is also a startup and recovery here which allows you to set
some stuff related to when the system blue screens,
you can see that here in the system failure part here and so it says
if you have a blue screen please write the data,
the dump file which is the snapshot of memory into this file.
However,
it's not really written in this file directly
because if the system blue screens,
it might be too dangerous at this point to write to some new file,
maybe the I.
O.
System is not in the pristine condition now and would be perhaps causing
even worse or causing some kind of damage to the system.
So instead the Cannon would want to write to the safest
location possible and that happens to be the page file
because the page file is already opened,
it's already there.
And so right into the page file is the safest thing to do.
Once it writes the kernel dump into the page file,
you restart the system and only when the system restarts.
Once the kernel starts in pristine condition,
it says that there is some dump in the page file and actually only
then copies that to the final file you specify here.
Now the problem is with this scheme is that if the page file is
not large enough to accommodate the dump,
you lose the dump and this is exactly what automatic
memory dump is trying to tell us here.
Automatic memory dump is this option that makes sure that the page
five size is configured in a particular way,
so that it with high probability will be big enough
to accommodate a potential dump.
And so if you decide to configure no dump file,
which of course you can do as we've seen,
you can just go ahead and say, I don't want any dump file here,
you will never get any kind of dump.
So if you don't want any page file,
you will not get any kind of dump and that's kind of a shame.
So even with this kind of case,
you still want to have some page file in case a blue screen occurs,
even though you might not need it in practice while
you're working normally with your system,
the automatic option here, automatic memory dump,
you can select here, which is also the default,
starting with Windows eight makes sure that you do have a dump file if if you
don't need it so that you at least will have a high chance of getting a blue
screen dump in case such a thing occurs now,
in terms of using and measuring that usage that you have
because the two week history is maintained and taking into
consideration the potential size of a dump,
then you get the page file size correctly configured by the kernel.
So today, in fact, I recommend you don't do anything with that setting.
Just let it be.