Quote:
I was under the impression that Windows 7 use C; for temp and that PD also used the c: drive
James1;
Just to clarify (or maybe confuse slightly) the issue, there are many kinds of temporary processes that create temporary files/pages.
Many DO NOT show when monitoring the space used on the drive, as the OS hides them and does NOT report the space as used.
Programs utilize algorithms of various kinds to control how processes occur and many of them DEFAULT to the OS drive whether there is a paging file there or not!! Eliminating the paging file on the OS drive can actually have a negative impact on program operation during paging, as it is then necessary for the program to create a temporary space "on-the-fly".
In 64BIT systems with large amounts of memory and high end CPUs and GPUs, the impact is reduced, but not ELIMINATED as memory-swaps and stitching are built in to the OS. Also, Legacy code snippets in supplementary programs (many of which are still 32BIT programs) are
hard-coded to use the OS drive and must reprocess if no space is allocated.
Intensive processes, like video transcoding, generate memory fragments that are off-loaded to the drive to be "stitched" together, even if memory is available. If the system has to move these processes to another drive, the CPU and the separate drive controllers must work harder and create latency that can impact performance.
It is not recommended that the paging file be eliminated from the OS drive. Like overclocking...some swear by it, and some curse it!! There are people who will argue vehemently on both sides! This is not a PowerDirector issue, it is part of the program design for Windows OS, and has been for many years!!
This message was edited 2 times. Last update was at Jan 03. 2012 23:38