public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Fast testing
Date: Wed, 15 Apr 2009 18:47:56 -0600	[thread overview]
Message-ID: <49E6803C.6010602@gmail.com> (raw)
In-Reply-To: <49E5D6D9.3040903@imap.cc>

Tilman Schmidt wrote:
> Tomasz Chmielewski schrieb:
>>> Wow. Nice machine. I wish I had one like that. And how long until
>>> the GUI is usable again and you can actually continue working?
>>>
>>> For comparison: my 3.4 GHz Pentium D takes 30 secs for kernel start
>>> (ie. until it begins looking for the filesystems),
>> Including all BIOS routines?
> 
> No - from hitting Enter in the GRUB menu.

That seems really high, unless you're using some storage driver that 
takes a really long time to initialize or something..

> 
>>>  2 mins until the graphical login screen appears, and
>>> 5 mins from logging in to the GUI being completely present.
>> I have an old 366 MHz / 192 MB machine which boots to GUI much faster.
> 
> Might depend on the value of "GUI". Mine wouldn't even load in 192 MB.
> Anyway, my preceding P3/700 MHz/512 MB box hasn't been much worse,
> either.
> 
>> Something's wrong with your setup (unless you start really lots of 
>> things or have some other, "uncommon" things).
> 
> Hmm, it's always been like that. As for "uncommon", this is a more
> or less out of the box openSUSE 10.3 installation. (Without Beagle,
> in case you were wondering.) Perhaps that's what's wrong? :-)
> 
> OTOH, even the GUIless CentOS server boxes I look after for a
> living take about 5 mins until they are up and running again after
> a kernel update - including BIOS, but without the fsck penalty.
> 
> Thanks,
> Tilman
> 


  reply	other threads:[~2009-04-16  0:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 12:19 Fast testing Tomasz Chmielewski
2009-04-15 12:45 ` Tilman Schmidt
2009-04-16  0:47   ` Robert Hancock [this message]
2009-04-16 15:19   ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2009-04-15 12:31 devzero
2009-04-15 12:49 ` Dragoslav Zaric
2009-04-14 14:44 Tomasz Chmielewski
2009-04-14  9:55 Dragoslav Zaric
2009-04-14 13:36 ` Alan Jenkins
2009-04-14 14:10   ` Dragoslav Zaric
2009-04-14 14:24   ` Dragoslav Zaric
2009-04-14 14:57     ` Cyrill Gorcunov
2009-04-14 13:53 ` Andi Kleen
2009-04-14 15:05 ` Arjan van de Ven
2009-04-14 16:44   ` Dragoslav Zaric
2009-04-15 11:48   ` Tilman Schmidt

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=49E6803C.6010602@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    --cc=tilman@imap.cc \
    /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