The suspend2 discussion resumes [LWN.net]

The suspend2 discussion resumes

Posted May 1, 2007 6:42 UTC (Tue) by bojan (subscriber, #14302)
In reply to: The suspend2 discussion resumes by xma
Parent article: The suspend2 discussion resumes

> s2d has never been quicker than a full shutdown/power up cycle

So, when you have 20 apps open, it is faster to shut down, reboot, log in, start the apps up again and return to exactly the spot where you've been X number of days ago (provided you can still remember)? I don't think so.

Suspend2 actually resumes very quickly (async I/O and multi-threaded decompression) and all apps are 100% responsive on resume, because Suspend2 saves the whole image of memory, unlike any other suspend to disk solution for Linux.

to post comments

The suspend2 discussion resumes

Posted May 1, 2007 7:51 UTC (Tue) by xma (guest, #44981) [Link] (1 responses)

First, it is unlikely I am running 20 apps at once. The basic situation
here is quite simple: GNU Screen + GNU emacs. When in X, I am running a
common lisp image containing my window manager and the sole X app I use is
konqueror).

Thus suspending/resuming (to disk) is useless for me (plus it often does
not suspend but crashes). I only use echo mem > /sys/power/state (s2r).

Maybe I am missing something.

The suspend2 discussion resumes

Posted May 1, 2007 8:02 UTC (Tue) by bojan (subscriber, #14302) [Link]

You obviuosly have a very simple situation.

I have 6 workspaces full of apps. Rebooting and getting to where I was is a painful exercise. Suspending to RAM is good, but what when I need to travel and take my notebook with me? I don't want to rely on my battery lasting through all this. And what if it comes out while the notebook is being handled by airport security?

Suspend to disk is the right thing to do for me. I get to exactly where I was in 30 seconds or so.