|
PureBytes Links
Trading Reference Links
|
Guys,
1. Dont install any utilities aka xp_pagefileMon, use
the task manager that comes with XP
2. In the performance page, look at your commit charge,
if that is less than your physical memory, your page file is doing nothing
except hogging space. you can safely reduce it to 0.5 physical
memory.
3. if you look at Msoft; statement of 1.5 times RAM
size - It is for general use without knowing what physical memory you have and
what kind of applications you run. now imagine you have 512MB of physical
memory, and with a pagefile of 1.5 time, you have 2GB of virtual memory. Now if
you go out and buy another 1.5 GB of ram, your physical memory is now the same
as your total virtual memory before and if 2GB of virtual was working
previously, you can now run it all in physical memory, and it doesnt make sense
to put away 6GB of disk space for pagefile for the same usage condition, In this
case, you can wind back the pagefile to say 1GB or less to cope with usual peak,
or no pagefile at all.
Paul
Hi J.,
Saturday, December 24, 2005, 3:17:47 AM, you
wrote:
JB> Just 2 comments:
JB> 1. Microsoft recommended in
the past a pagefile 1.5 times
JB> the RAM size.
I know. They
have never changed it. Just laziness I think. It's a
formula that
has no rational basis in fact now that memory amounts go
well beyond what MS
ever imagined at the time they first wrote the
suggestion.
JB> 2.
it is not the resizing of the page file that is the drag
JB> on
performance, it is the resulting defragmented pagefile
JB> which is the
drag.
It's both. But constant resizing for no other reason than the
OS has
an algorithm to do so, will certainly contribute to
fragmentation.
Yuki
Please note that this group is for discussion between users only.
To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com
For other support material please check also:
http://www.amibroker.com/support.html
SPONSORED LINKS
YAHOO! GROUPS LINKS
|