Do you leave the pagefile on your ssd, or do you move it to your D (spinner) drive?
Many user have the OS on a ssd C:/, and use a hdd for data as the D:/ drive. I have always moved the pagefile to a seperate drive (spinner) because it A: reduces the read/writes to the ssd, B: frees up some space, important if you only have a 60-120gb ssd, and C: on a separate drive it does not compete for read/write time that other apps may be doing on the OS drive. I also set the pagefile at a fixed size, the same as the amount of memory the machine has up to 8gb. If you run with dozens of open apps you may want to go as high as 16gb.
Good read on Page Files.
After some reading about this I think my concern about ssd read/writes may be flawed thinking. Any additional read/write caused by the page file is insignificant on the newest generation of ssd's, although earlier ssd's can have wear leveling issues...reportedly.
My thinking on a fixed size for the page file is primarily it will be one continuous block on the drive, and should not become fragmented, assuming you create the file on a fresh drive.
If you take the time to google this subject you well see a lot of really smart software engineers and tech guys argue, sometimes very heatedly. Bottom line, do what works for your conditions.
Many user have the OS on a ssd C:/, and use a hdd for data as the D:/ drive. I have always moved the pagefile to a seperate drive (spinner) because it A: reduces the read/writes to the ssd, B: frees up some space, important if you only have a 60-120gb ssd, and C: on a separate drive it does not compete for read/write time that other apps may be doing on the OS drive. I also set the pagefile at a fixed size, the same as the amount of memory the machine has up to 8gb. If you run with dozens of open apps you may want to go as high as 16gb.
Good read on Page Files.
After some reading about this I think my concern about ssd read/writes may be flawed thinking. Any additional read/write caused by the page file is insignificant on the newest generation of ssd's, although earlier ssd's can have wear leveling issues...reportedly.
My thinking on a fixed size for the page file is primarily it will be one continuous block on the drive, and should not become fragmented, assuming you create the file on a fresh drive.
If you take the time to google this subject you well see a lot of really smart software engineers and tech guys argue, sometimes very heatedly. Bottom line, do what works for your conditions.
My Computer
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Custom, Dell and Lenono LT's
- OS
- Win8/8.1,Win7-U64, Vista U64, uncounted Linux distor's
- CPU
- AMD and Intell, 9590, 8350, i5 3570k
- Motherboard
- CFVFZ, GA990FXA, Z77e-itx
- Memory
- Corsair G Skill
- Graphics Card(s)
- Crossfired Sapphire HD 7950 Vapor-X, ASUS R9 280X TOP
- Sound Card
- Realtek ALC889
- Monitor(s) Displays
- ViewSonic VX2770SMH 27" / ViewSonic VX2433 LCD 24"
- Screen Resolution
- 1080i HD
- Hard Drives
- Samsung SSD 840 Pro
OCZ Agility 3's
OCZ Vector's
WD's Blue, red, green, Velociraptors
Seagate USB3 & Hybrid's
ASUS Blu-Ray
ASUS DVD
- PSU
- Corsair AX1200i, Seasonice 850 Gold
- Case
- Cooler Master HAF 922 & HAF 932, Lian Li Train case.
- Cooling
- Air, Glacer 240L expanded, custom EK loop with duel D5's
- Keyboard
- Microsoft SideWinder X4 USB Keyboard / Logitech 250 PS2
- Mouse
- Logitech G500 / MS wireless 5000
- Internet Speed
- Best of 5ms / 75+ dn / 12+ up More or less.
- Antivirus
- MS esentials-MalwareBytes
- Browser
- Firefox Chromebook