I have a very specific problem with the way XP manages memory that I would
like to improve. Its hard for me to explain but here goes -
I use my pc for general web surfing, games, writing cd/dvds and p2p programs
like Emule and Bittorrent. If I use my PC one night for a while it runs
smoothly. The next night after letting the p2p programs run and leaving IE6
and windows explorer minimized it does some serious disk thrashing to
restore IE6 and WE and scroll through the start menu to start another app.
After a lot of research I think XP has decided that because IE6, WE and the
start menu icons have been idle for a while it has paged them to disk.
Instead it has used the memory for file caching the p2p programs data. It
also seems to page out most of the p2p programs themselves as restoring them
from the tray takes a while too.
In my view this is futile and unhelpful. I would much rather have fast and
responsive switching between apps and scrolling through the start menu than
a tiny (negligable) gain in file caching. The reason I think the gain in
file caching is useless is because the two p2p are addressing between 10 and
50gb of data to *many* peers so the chances of a successful cache hit are
low. Also the the data transfer rate is only about 100k/s so any gain in
speed (or reduction in disk reading) would be very small. I guess about 3gb
of p2p data is transferred per day.
The only way I can think of to stop XP paging idle programs to hard disk is
to create a Ramdisk. Now I know that usually Ramdisks are a waste of time
but in this specific case I think it could help. I have 1024mb of ram and
would allocate about 150-250mb to a ramdisk pagefile and also have a hard
disk page file of about 1024mb. I guess that the ramdisk pagefile would be
used for paging the kernel/idle progs etc unitl it was filled, only then
would the hard disk page file would be used. This way the 2 or 3 idle progs
would be paged to the ramdisk and would snap back to life when I need them.
However I am not sure if the ramdisk would be filled first then the hard
disk pagefile or if XP would page the data wherever it wants. Overall I
rarely seem to run out of memory when playing a game or using an app.
Restoring apps that have been paged to disk is my only memory related
problem.
I suspect that even with 2gb ram the idle apps would be paged to disk if 3gb
or more data was transferred via p2p. Does anyone have a better suggestion
to stop the disk thrashing when I first use the PC after a nights p2p
activty ?
like to improve. Its hard for me to explain but here goes -
I use my pc for general web surfing, games, writing cd/dvds and p2p programs
like Emule and Bittorrent. If I use my PC one night for a while it runs
smoothly. The next night after letting the p2p programs run and leaving IE6
and windows explorer minimized it does some serious disk thrashing to
restore IE6 and WE and scroll through the start menu to start another app.
After a lot of research I think XP has decided that because IE6, WE and the
start menu icons have been idle for a while it has paged them to disk.
Instead it has used the memory for file caching the p2p programs data. It
also seems to page out most of the p2p programs themselves as restoring them
from the tray takes a while too.
In my view this is futile and unhelpful. I would much rather have fast and
responsive switching between apps and scrolling through the start menu than
a tiny (negligable) gain in file caching. The reason I think the gain in
file caching is useless is because the two p2p are addressing between 10 and
50gb of data to *many* peers so the chances of a successful cache hit are
low. Also the the data transfer rate is only about 100k/s so any gain in
speed (or reduction in disk reading) would be very small. I guess about 3gb
of p2p data is transferred per day.
The only way I can think of to stop XP paging idle programs to hard disk is
to create a Ramdisk. Now I know that usually Ramdisks are a waste of time
but in this specific case I think it could help. I have 1024mb of ram and
would allocate about 150-250mb to a ramdisk pagefile and also have a hard
disk page file of about 1024mb. I guess that the ramdisk pagefile would be
used for paging the kernel/idle progs etc unitl it was filled, only then
would the hard disk page file would be used. This way the 2 or 3 idle progs
would be paged to the ramdisk and would snap back to life when I need them.
However I am not sure if the ramdisk would be filled first then the hard
disk pagefile or if XP would page the data wherever it wants. Overall I
rarely seem to run out of memory when playing a game or using an app.
Restoring apps that have been paged to disk is my only memory related
problem.
I suspect that even with 2gb ram the idle apps would be paged to disk if 3gb
or more data was transferred via p2p. Does anyone have a better suggestion
to stop the disk thrashing when I first use the PC after a nights p2p
activty ?