Subject: | |
From: | |
Reply To: | |
Date: | Thu, 25 May 2000 23:32:16 +0300 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 25 May 2000, at 23:53, Ultra <[log in to unmask]> wrote:
> Mark alreay answered your questions, however here is my exp on it. I'm
> using 600M fixed swap file, Windows load up everything faster, because
> windows doesn't need to locate disk space from everywhere on harddisk.
a) I thought that during the OS load up, the swap file is not yet in use,
because at least at the begining, the RAM is enough.
b) As I said in my reply to Mark (night distributed after yours depending
on the approval), the crucial point in my second example (the example
with the non-fixed size swap file), is the use of a dedicated logical drive
(the first of a physical drive) only for the swap file. I cannot see why the
problem of fragmentation will occur there - there is only one file in the
drive.
> Get a large fixed swap file will also help to avoid "out of disk space" problem
> sometimes (you know someone would like to use every bit of his harddisk, so
> he will create problem when free disk space is low. I have some cases that
> users only have 30M disk space left and still thinks they have large amount
> of space to use. In cases like this, pre-take 400M swap space away will be
> the best bet.)
Let alone the problem of no space for temporary files that might cause
problems, I believe that windows (in non-fixed size swap file) will know
not to produce swap file larger than the space it has (on account of
caching).
My questions are mainly in order to understand things, not in order to
get a recommendation.
Uzi
Do you want to signoff PCBUILD or just change to
Digest mode - visit our web site:
http://nospin.com/pc/pcbuild.html
|
|
|