2 ms·
No performance issue for non-holey files, and the meaning of swap gets really really weird when you have 32 or 64GB of RAM. Ever since 16GB+ servers I've had no
by ChuckMcM 10y ago
No performance issue for non-holey files, and the meaning of swap gets really really weird when you have 32 or 64GB of RAM. Ever since 16GB+ servers I've had no swap partition, and a 1GB swap file, if the swap file ever gets touched I figure out what was screwing up and fix it (I consider it an error to swap in my systems).
It is perhaps not too surprising but if you ever swap to a non-SSD device you're effective computation rate is reduced by 3 orders of magnitude.
- rebootthesystem 10y agoI've been using a small dedicated SSD drive for swap file and other temp file requirements for a few years now. One example of this is Photoshop temp file space. I don't want unnecessary I/O out of system or data drives. That said, yes, we just got done upgrading all of our workstations to new self-built systems with 64 GB of RAM and I would definitely consider having to go to swap file to be an error. All of our systems have 5 SSD drives: System, Data, Library, Development, Swap. They are all 1 TB SSD's with the exception of the 256 GB Swap/Temp drive. The idea is to distribute read/writes and organize things so that no SSD, and, in particular, the system SSD, is abused. Running a large number of FEA thermal simulations or a bunch of FPGA compilation jobs can produce an amazing amount of files. This approach seems to do a decent job of spreading that out and keeping it off the System drive. That, coupled with local (network) and remote backups has worked well so far.