That works if there is enough memory after the "bad" process has been killed. The question is, is it necessary? Many systems can live with processes performing a little bit poorly for some minutes and I wouldn't do it.

▲

creer 3 days ago | parent | next [-]

It's fine that "many systems" can. But there is no easy way when the user or system can't. Flushing back to RAM is slow - that's not controversial. So it would help if there was a way to do this in advance of the need for the programs where that matters.

	▲	aeonik 3 days ago \| parent [-]
		You mean like vmtouch and madvise? I use vmtouch all the time to preload or even lock certain data/code into RAM.

▲

michaelt 3 days ago | parent | prev [-]

> The question is, is it necessary? Many systems can live with processes performing a little bit poorly for some minutes and I wouldn't do it.

The outage ain't resolved until things are back to operating normally.

If things aren't back to 100% healthy, could be I didn't truly find the root cause of the problem - in which case I'll probably be woken up again in 30 minutes when the problem comes back.

	▲	whatevaa 3 days ago \| parent [-]
		Desktops are not servers. There could be no problem, just some hungry legitimate program (or vm).