News for hackers. Stuff that matters.
Re:Swap, swap, swap, and bad places to work by gok on Friday August 09, 2019 @11:52AM (#20655478)
Swap is best seen as a component of the "bad idea trinity", next to fork() and overcommit.
Re:Swap, swap, swap, and bad places to work by erik_seaberg on Friday August 09, 2019 @01:44PM (#20656642)
If you need a network server to respond in 40 ms p99, letting it start swapping is crazy. But it made sense for timesharing undersized computers running jobs that take minutes or hours. You overcommit because your institution couldn't afford two computers.

I/O also used to have a smaller speed penalty. There was just one core and it wasn't so dramatically faster than the rest of the machine. Hell, there used to be faster disks for swap than for the filesystem, and tuning was about scheduling jobs and placing inputs and outputs so as to fully utilize the fs disks.

Re:Swap, swap, swap, and bad places to work by pixl97 on Friday August 09, 2019 @02:12PM (#20656926)
I dont know if I would say 'used to be', things like Optane are essentially a ssd memory/disk tier. If it's running in bit addressable mode you can consider it a swap tier between memory and disk/network.