home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!kuhub.cc.ukans.edu!parsifal.umkc.edu!vax1.umkc.edu!edowdy
- Newsgroups: comp.os.ms-windows.setup
- Subject: Re: swapfile location
- Message-ID: <1992Sep15.111625.1@vax1.umkc.edu>
- From: edowdy@vax1.umkc.edu
- Date: Tue, 15 Sep 1992 17:16:25 GMT
- Sender: root@parsifal.umkc.edu (Parsifal Administration)
- References: <1992Sep1.071417.7517@megadata.mega.oz.au> <Bu4w4A.29w@belay> <1992Sep10.162824.18973@microsoft.com>
- Organization: University of Missouri - Kansas City
- Lines: 27
-
- In article <1992Sep10.162824.18973@microsoft.com>, t-ericj@microsoft.com (Eric Johnson) writes:
- > In article <Bu4w4A.29w@belay> fournes@belay (Who, me?) writes:
- >>In article <1992Sep1.071417.7517@megadata.mega.oz.au> vince@megadata.mega.oz.au (Vince Sandrone) writes:
- >>>in a multiple harddisk environment is it quicker to
- >>>have the permanent swapfile on the SAME or Different
- >>>harddisk to Windows (everything else being equal)
- >>>
- >>>thanks in advance
- >>
- >>I would think the same drive as womdpws (or most of the apps/data that
- >>you would be running/reading) would make it faster, since then the
- >>read/write heads wouldn't have as far to travel between swap and
- > ^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
- >>application/data.
- > ^^^^^^^^^^^^^^^^
- >
- >
- > I don't know exactly what the answer is; but your reasoning is faulty.
- > If the swapfile is on a disk other than Windows and apps, then then heads
- > don't have to move at all -- each drive has its own set of heads.
- > I'd put the swapfile on the disk with the lowest access time; if they are
- > the same, I'd put them on the disk that does NOT have windows, so those
- > heads can stay on windows and its apps, and the other set of heads
- > can stay on the swapfiles.
- >
-
- OR..........You could buy more memory resulting in even less disk access time.
-