Hpw to disable message that pagefile is increasing?

  • Thread starter Thread starter Howard Kaikow
  • Start date Start date
H

Howard Kaikow

I am further confused by paging files.

I had a fixed 64MB file on drive C and a variable 64-1152MB file on Drive G,
OS is on J,

Rarely, does page file use get above 30MB in either (see
http://www,standards.com/index.html?PageFileUsageMonitor ).

However, last night, while building the Retrospect catalog and downloading
some files, I got a message stating that the page file was being increased
to 131MB. I know not why it needed that space, system has 768MB of memory.

I am confused as to why the file size was not just silently increased within
the limit of 64 + 1152.

Such a message makes the computer wait until I respond. Not very nice.

How do I prevent such a message?
 
Just make the pagefile the size of the physical RAM, 768MB.

--
Dave




| I am further confused by paging files.
|
| I had a fixed 64MB file on drive C and a variable 64-1152MB file on Drive G,
| OS is on J,
|
| Rarely, does page file use get above 30MB in either (see
| http://www,standards.com/index.html?PageFileUsageMonitor ).
|
| However, last night, while building the Retrospect catalog and downloading
| some files, I got a message stating that the page file was being increased
| to 131MB. I know not why it needed that space, system has 768MB of memory.
|
| I am confused as to why the file size was not just silently increased within
| the limit of 64 + 1152.
|
| Such a message makes the computer wait until I respond. Not very nice.
|
| How do I prevent such a message?
| --
| http://www.standards.com/; See Howard Kaikow's web site.
|
|
 
You need to decide if you are going to check your Memory Dump if the system
crashes.

If the answer is no, then set your System Drive Pagefile to 0 - 0
and your Data Drive Pagefile to 2 x RAM - 2 x RAM

And set the Memory Dump setting under "Startup and Recovery" to (none)

NEVILLE
 
Neville said:
You need to decide if you are going to check your Memory Dump if the system
crashes.
Click to expand...

No interest in memory dumps.
If the answer is no, then set your System Drive Pagefile to 0 - 0
and your Data Drive Pagefile to 2 x RAM - 2 x RAM
Click to expand...

The only page file is now 64-1152 on the G drive, main OS is on J.
None on any of the other drives.
And set the Memory Dump setting under "Startup and Recovery" to (none)
Click to expand...

It was set to small memory dump (64KB), now it is set to none, at least it
will be after my next reboot.
 
Then add more physical RAM.

It's your choice.

--
Dave




| That's a waste of space.
 
Are these pagefiles and operating system on separate physical hard
drives or are they on separate partitions only? Windows will always use
the pagefile no matter how much RAM you have on the machine, that's just
a fact of life with Windows. About one of the worse performance hits
that can be had with pagefile is to have it resize and become
fragmented. That is why it is usually suggested that you set a static
size for it and that you make it large enough to accommodate paging
requirements. You have already seen that despite having quite adequate
RAM on your machine (768MB) Windows requested an extra 130 some MB more
during an operation that you were performing. You have already decided
to allocate 1152 megabytes to the pagefile (64-1152) so you may as well
just set a static pagefile of 1152MB.

John
 
John John said:
Are these pagefiles and operating system on separate physical hard
drives or are they on separate partitions only? Windows will always use
the pagefile no matter how much RAM you have on the machine, that's just
a fact of life with Windows. About one of the worse performance hits
that can be had with pagefile is to have it resize and become
fragmented. That is why it is usually suggested that you set a static
size for it and that you make it large enough to accommodate paging
requirements. You have already seen that despite having quite adequate
RAM on your machine (768MB) Windows requested an extra 130 some MB more
during an operation that you were performing. You have already decided
to allocate 1152 megabytes to the pagefile (64-1152) so you may as well
just set a static pagefile of 1152MB.
Click to expand...
C is on Drive 0, F and G are on DRive 1, J is on DRive 2.

The pagefile use rarely hits 30MB.

It must have been Retrospect's rebuilding of a catalog that caused this to
increase to 131.
I just rebooted a couple of minutes ago, current use is 21MB, max was 24MB
since the boot.
Almost always stays nelow 30MB.

J is the main OS, so having the pagefile on G reduces thr disk seek hits.

I'll keep an eye of usage.
 
Bring the platform to 1GB

--
Dave




| The pagefile use rarely hits 30MB.
|
| It must have been Retrospect's rebuilding of a catalog that caused this to
| increase to 131.
| I just rebooted a couple of minutes ago, current use is 21MB, max was 24MB
| since the boot.
| Almost always stays nelow 30MB.
|
| J is the main OS, so having the pagefile on G reduces thr disk seek hits.
|
| I'll keep an eye of usage.
 
Then bring up the size of the VM file or get a new motherboard that allows more RAM.
Otherwise the error message can be expected.

--
Dave





| 768 MB is the max allowed.
|
|
 
David H. Lipman said:
Then bring up the size of the VM file or get a new motherboard that allows more RAM.
Otherwise the error message can be expected.
Click to expand...

I've seen the pagefile size increase without getting the message, so there
is something else going on here.
 
Back
Top