Skip to contentSkip to conversation

Fast testing

DISCUSSION Tomasz Chmielewski 4 participants 4 messages Apr 15, 2009 – Apr 16, 2009

lore
Share & tools
lore
#0 lore raw
Quoted 5 lines

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?

Quoted 2 lines

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.

Something's wrong with your setup (unless you start really lots of things or have some other, "uncommon" things).

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#1 lore raw
Quoted 7 lines · Tomasz Chmielewski
Quoted 5 lines

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.

Quoted 4 lines
Quoted 2 lines

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.

Quoted 2 lines

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

Signature · 4 lines
Tilman Schmidt                    E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
#2 lore raw
Quoted 9 lines · Tilman Schmidt
Quoted 6 lines · Tomasz Chmielewski
Quoted 5 lines

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..

Quoted 22 lines
Quoted 4 lines
Quoted 3 lines

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.

Quoted 1 line

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

#3 lore raw
In reply to Tilman Schmidt
Quoted 6 lines · Tilman Schmidt
Quoted 2 lines

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? :-)

Umm... shot in the dark - memory incorrectly flagged as non-cachable by an mtrr?