Re: partioning HD w/NTFS


"Richard Urban" <richardurbanREMOVETHIS@xxxxxxxxxxx> wrote in message
news:OnFdxftTGHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
Wrong. If something wants to read from the pagefile at the same time the other drive is
writing to disk, the pagefile read gets bumped momentarily.

***
Are we discussing this relative to 2 HDs on two different IDE controllers?

Even if we serialize access between the pagefile and non-pagefile files/folders, head seek
will have been minimized for the pagefile if on a separate PHYSICAL drive (not separate
partition on same drive as C:).

You also say that the pagfile read gets bumped momentarily. That implies the priority of
pagefile I/Os is always LOWER than other I/Os (i.e. bringing new DLLs/EXEs into memory).
Even if that's true, reducing seek times for pagefile access even if on the same IDE
controller is better than leaving the pagefile on the C: partition.


It will have an adverse effect on your system. It is better to leave it on drive C that
to place it on a second drive on the same IDE controller. You gain NOTHING by placing it
on the second drive - same controller. You, in fact, lose.

***
Obviously having the pagefile on a separate IDE controller is potentially better (i.e.
assume we do have some pagefile I/Os). But having the heads on the 2nd PHYSICAL drive
attached to the SAME IDE controller is still potentially better (head seek) than having
the pagefile on the C: partition/hard drive.

JL


--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Jim Lewandowski" <jlewand@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eunUf.3097$4L1.2303@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

"Richard Urban" <richardurbanREMOVETHIS@xxxxxxxxxxx> wrote in message
news:ew7ffyhTGHA.2656@xxxxxxxxxxxxxxxxxxxxxxx
Placing the pagefile on a slave drive (connected to the same IDE channel) buys you a
sum total of nothing.

***
Not so. By having the paging file reside on another drive, at least he can minimize
head (seek) movement. That's worth about 10 ms saved per seek. Again, if the paging
file is the ONLY file being accessed on the second hard drive or the one primarily
being accessed (few intervening files read off same drive of other files/folders), that
would be of benefit as the heads would always be parked right where Windows paging
subsystem would like them to be.

Remember, lots of background CONTINUAL disk accesses can/do occur with Windows/XP (NAV,
system tasks, NTFS logging).

Additionally, when physical paging occurs, it is usually a SYNCHRONOUS process to "real
work" (user applications) within the system . IOW, an applications use of memory has
caused Windows to physically page out other blocks of memory. Is there ever paging
file activity at the same time for OTHER disk accesses? Not likely. It can happen if
one is launching a new program (reading exe/dll stuff into memory forcing physical disk
paging into action).


In fact, it may slow the system down. The
two drives write consecutively. When one drive is in read/write mode the other drive
CAN NOT do the same. The time is split between the two drives.

***
See head/seek placement issue above.



Place the pagefile on a hard drive on the secondary IDE controller and you can have
concurrent reading/writing of BOTH drives. Here you will likely see a gain if you are
using programs that make extensive use of the pagefile.

***
The final question is: what % of the time is your paging file PHYSICALLY being written
to/read from?

JL


--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"jsph1961" <jsph1961@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4206477E-03D0-46D5-9BEE-5F5B874B69C7@xxxxxxxxxxxxxxxx
I have 2 HDs on my PC, on the master (80GB) I have XP pro and everything
else. On the slave(40GB)I put a paging file and nothing else. I want to
partition so that my O/S is alone on the master ;so what size will suffice
for the O/S? I then want to put all the hot fixes into a folder on a seperate
partition. Then all my games on another then text files on another and so
on... Also concerning paging file. By having the paging file on a different
HD other than where the O/S is I'm concerned about the memory dump. How
large should I make the paging file on the master to handle the memory dump?
And how large should the paging file be on the slave which is accessed less?
I have 1 GB of memory to play with. Will the /S be able to access the games
even if they are on a HD without an O/S on it?








.

Relevant Pages

  • Re: Pagefile.sys corrupted
    ... When you reboot into normal mode, the pagefile will get ... > Windows partition exists. ... > the min=max settings for virtual memory (on both drives), ... I then found that any attempt to opt for a custom size paging file, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: pagefile.sys?
    ... It is recommended that a small pagefile say 50 mb is kept on the system ... Right now, I have removed the> pagefiles on all drives in windows in the virtual memory allocation> window, ... The paging file is a temporary storage space that>>>> your ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: partioning HD w/NTFS
    ... other drive is writing to disk, the pagefile read gets bumped momentarily. ... if the paging file is the ONLY file being accessed on the ... you can have concurrent reading/writing of BOTH drives. ...
    (microsoft.public.windowsxp.general)
  • Re: partioning HD w/NTFS
    ... This whole thread is about two drives on either one IDE channel or two drives on two IDE ... obviously having each drive on its own IDE controller offers the maximum ... By having the paging file reside on another drive, ...
    (microsoft.public.windowsxp.general)
  • Re: Pagefile Problems...
    ... There follows the detailed procedures for Moving the Paging File -they ... one on which Windows is installed (Windows is usually installed on the ... Under Total paging file size for all drives, ... > Thnx for th eclarificatoin..I thought I was limiting the pagefile ...
    (microsoft.public.windowsxp.perform_maintain)