From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Willi Mann <foss-ml@wm1.at>
Cc: linux-pm@lists.linux-foundation.org, linux-pm@lists.osdl.org
Subject: Re: kernel 2.6.32 much slower than 2.6.31 on s2disk
Date: Mon, 28 Dec 2009 23:56:26 +0100 [thread overview]
Message-ID: <200912282356.26815.rjw@sisk.pl> (raw)
In-Reply-To: <4B386B89.6000506@wm1.at>
On Monday 28 December 2009, Willi Mann wrote:
>
> >> I don't know to how to do a reliable benchmark on this problem, espially as
> >> the required time probably very much depends on the exact state of the
> >> frozen system. Is there any change in 2.6.32 that might cause less memory to
> >> be stored on the suspend device, and thus require more random disk access
> >> after the restore?
> >
> > Actaully, yes, there is.
> >
> > Please try to increase the value in /sys/power/image_size to approximately
> > 1/2 of your RAM and report back (the number is in bytes).
>
> Without changing the image_size, it especially got much better when I
> downgraded QT 4.6 to QT 4.5 which does not work well with KDE 4.3 (seems
> to cause memleaks).
>
> However, image_size is already set to your recommended value (well,
> approximately):
>
> # cat /sys/power/image_size
> 951431086
>
> My RAM size is 2 GB (however, I have intel graohics with shared mem, so
> some part is reserved), my swap size is a little bit more than 2 GB.
>
> I don't know what value image_size was set to when I tried first.
>
> Note that when I reported the issue first I used Debian kernel 2.6.32-1,
> (probably plain 2.6.32), while I'm now using Debian kernel 2.6.32-2
> (according to the changelog 2.6.32.1)
So, is it still a problem for you?
Rafael
next prev parent reply other threads:[~2009-12-28 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 16:10 kernel 2.6.32 much slower than 2.6.31 on s2disk Willi Mann
2009-12-17 7:31 ` Willi Mann
2009-12-27 20:56 ` Rafael J. Wysocki
2009-12-28 8:25 ` Willi Mann
2009-12-28 22:56 ` Rafael J. Wysocki [this message]
2009-12-31 9:54 ` Willi Mann
2009-12-31 11:01 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200912282356.26815.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=foss-ml@wm1.at \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-pm@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox