From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: Nigel Cunningham <nigel@suspend2.net>,
Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] swsusp: support creating bigger images
Date: Thu, 27 Apr 2006 17:27:38 +0200 [thread overview]
Message-ID: <200604271727.39194.rjw@sisk.pl> (raw)
In-Reply-To: <200604251231.57577.rjw@sisk.pl>
Hi,
On Tuesday 25 April 2006 12:31, Rafael J. Wysocki wrote:
> On Tuesday 25 April 2006 12:04, Pavel Machek wrote:
> > > > Okay, so it can be done, and patch does not look too bad. It still
> > > > scares me. Is 800MB image more responsive than 500MB after resume?
> > >
> > > Yes, it is, slightly, but I think 800 meg images are impractical for
> > > performance reasons (like IMO everything above 500 meg with the current
> > > hardware). However this means we can save 80% of RAM with the patch
> > > and that should be 400 meg instead of 250 on a 500 meg machine, or
> > > 200 meg instead of 125 on a 250 meg machine.
> >
> > Could we get few people trying it on such small machines to see if it
> > is really that noticeable?
>
> OK, I'll try to run some tests on a machine with smaller RAM (and slower CPU).
Done, although it was not so easy to find the box. This was a PII 350MHz w/
256 MB of RAM.
I invented the following test:
- ran KDE with 4 desktops,
- ran Firefox, OpenOffice.org 1.1 (with a simple spreadsheet), and GIMP (with
2 pictures) each on its own desktop,
- ran the memory meter from the KDE's Info Center and two konsoles
on the remaining desktop - one konsole with a kernel compilation and the
other with a root session used for suspending the box (the built-in swsusp
was used),
so the box's RAM was almost fully occupied with ~30% taken by the page cache.
Then I suspended the box and measured the time from the start of resume
(ie. leaving GRUB) to the point at which I had all of the application windows
fully rendered on their respective desktops (I always switched the desktops
in the same order, starting from the memory meter's one, through the OOo's
and Firefox's, finishing on the GIMP's one and I always switched the
desktop as soon as the window(s) on it were fully rendered).
I ran it a couple of times on the 2.6.17-rc1-mm2 kernel with and without
the patch and the results (on the average) are the following:
(a) 25-28s with the patch
(b) 30-33s without it
Moreover, with the patch the image size was about 49000 of pages (only
~7000 - 12000 pages had to be copied during suspend) and without the patch
it was about 30000 of pages, so with the patch much smaller number of
pages was in the swap after resume.
Greetings,
Rafael
next prev parent reply other threads:[~2006-04-27 15:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 21:55 [RFC][PATCH] swsusp: support creating bigger images Rafael J. Wysocki
2006-04-24 22:16 ` Pavel Machek
2006-04-25 8:26 ` Rafael J. Wysocki
2006-04-25 10:04 ` Pavel Machek
2006-04-25 10:31 ` Rafael J. Wysocki
2006-04-27 15:27 ` Rafael J. Wysocki [this message]
2006-04-27 20:55 ` Pavel Machek
2006-04-28 9:19 ` Rafael J. Wysocki
2006-04-28 9:23 ` Pavel Machek
2006-04-25 10:28 ` Nick Piggin
2006-04-25 15:39 ` Rafael J. Wysocki
2006-04-25 20:32 ` Pavel Machek
2006-04-25 21:12 ` Rafael J. Wysocki
2006-04-25 21:18 ` Nigel Cunningham
2006-04-25 22:21 ` Rafael J. Wysocki
2006-04-25 22:24 ` Nigel Cunningham
2006-04-25 22:38 ` Rafael J. Wysocki
2006-04-25 22:25 ` Pavel Machek
2006-04-25 22:30 ` Nigel Cunningham
2006-04-25 22:36 ` Pavel Machek
2006-04-25 22:43 ` Rafael J. Wysocki
2006-04-26 0:49 ` Nigel Cunningham
2006-04-30 12:27 ` Rafael J. Wysocki
2006-05-01 1:49 ` Nigel Cunningham
2006-05-01 11:20 ` Rafael J. Wysocki
2006-05-01 22:56 ` Nigel Cunningham
2006-04-26 2:24 ` Nick Piggin
2006-04-26 3:41 ` Nigel Cunningham
2006-04-26 16:22 ` Nick Piggin
2006-04-26 21:16 ` Rafael J. Wysocki
2006-04-26 8:10 ` Pavel Machek
2006-04-27 19:53 ` [RFC][PATCH] swsusp: support creating bigger images (rev. 2) 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=200604271727.39194.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=nigel@suspend2.net \
--cc=pavel@suse.cz \
/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