Skip to main content
Super User

Return to Answer

replaced http://serverfault.com/ with https://serverfault.com/
Source Link
Community Bot
Community Bot
  • 1
  1. Let there be a 4GB swapfile on the SSD to raise my commit charge, so I can use all the physical memory. But a swapfile on the SSD will degrade the SSD faster and slow down performance anytime Windows decides to put something important in the swapfile.

(my boldface)

The above is a myth. In a reasonable workload and with a properly spec'd SSDand with a properly spec'd SSD flash endurance isn't what will kill your drive within any reasonable amount of time. The exception to this is pretty much if the drive is faulty to begin with, which is what warranty is supposed to cover.

Swap space has significant uses even when there is plenty of RAM available.

Just put some swap on the SSD. A few gigabytes is likely plenty, but this depends on your typical and peak (memory-wise) workloads. If your system has plenty of RAM compared to its normal workload, it's likely that the swap won't see much use, but the swap space will be there if the memory manager decides that using swap is a better tradeoff than evicting cache from RAM. If your system is routinely memory starved, then you definitely want swap for now; add some more RAM later on and keep the swap space around for exceptional loads.

  1. Let there be a 4GB swapfile on the SSD to raise my commit charge, so I can use all the physical memory. But a swapfile on the SSD will degrade the SSD faster and slow down performance anytime Windows decides to put something important in the swapfile.

(my boldface)

The above is a myth. In a reasonable workload and with a properly spec'd SSD flash endurance isn't what will kill your drive within any reasonable amount of time. The exception to this is pretty much if the drive is faulty to begin with, which is what warranty is supposed to cover.

Swap space has significant uses even when there is plenty of RAM available.

Just put some swap on the SSD. A few gigabytes is likely plenty, but this depends on your typical and peak (memory-wise) workloads. If your system has plenty of RAM compared to its normal workload, it's likely that the swap won't see much use, but the swap space will be there if the memory manager decides that using swap is a better tradeoff than evicting cache from RAM. If your system is routinely memory starved, then you definitely want swap for now; add some more RAM later on and keep the swap space around for exceptional loads.

  1. Let there be a 4GB swapfile on the SSD to raise my commit charge, so I can use all the physical memory. But a swapfile on the SSD will degrade the SSD faster and slow down performance anytime Windows decides to put something important in the swapfile.

(my boldface)

The above is a myth. In a reasonable workload and with a properly spec'd SSD flash endurance isn't what will kill your drive within any reasonable amount of time. The exception to this is pretty much if the drive is faulty to begin with, which is what warranty is supposed to cover.

Swap space has significant uses even when there is plenty of RAM available.

Just put some swap on the SSD. A few gigabytes is likely plenty, but this depends on your typical and peak (memory-wise) workloads. If your system has plenty of RAM compared to its normal workload, it's likely that the swap won't see much use, but the swap space will be there if the memory manager decides that using swap is a better tradeoff than evicting cache from RAM. If your system is routinely memory starved, then you definitely want swap for now; add some more RAM later on and keep the swap space around for exceptional loads.

Source Link
user
user
  • 30k
  • 11
  • 103
  • 147

  1. Let there be a 4GB swapfile on the SSD to raise my commit charge, so I can use all the physical memory. But a swapfile on the SSD will degrade the SSD faster and slow down performance anytime Windows decides to put something important in the swapfile.

(my boldface)

The above is a myth. In a reasonable workload and with a properly spec'd SSD flash endurance isn't what will kill your drive within any reasonable amount of time. The exception to this is pretty much if the drive is faulty to begin with, which is what warranty is supposed to cover.

Swap space has significant uses even when there is plenty of RAM available.

Just put some swap on the SSD. A few gigabytes is likely plenty, but this depends on your typical and peak (memory-wise) workloads. If your system has plenty of RAM compared to its normal workload, it's likely that the swap won't see much use, but the swap space will be there if the memory manager decides that using swap is a better tradeoff than evicting cache from RAM. If your system is routinely memory starved, then you definitely want swap for now; add some more RAM later on and keep the swap space around for exceptional loads.