From Fedora Project Wiki

(add me to the results table (results coming))
Line 91: Line 91:
 
| [[User:dkovalsk | David Kovalský]]  
 
| [[User:dkovalsk | David Kovalský]]  
 
| [http://www.smolts.org/client/show/pub_e554952e-e40e-4990-ba25-c7b1b8dcf172 HW]
 
| [http://www.smolts.org/client/show/pub_e554952e-e40e-4990-ba25-c7b1b8dcf172 HW]
 +
| <!-- Bootchart - my setup -->
 +
| <!-- Bootchart - desktop -->
 +
| <!-- Bootchart - server -->
 +
| <!-- Bootchart - minimal -->
 +
| <!-- Comments -->
 +
|-
 +
| [[User:Adamwill | Adam Williamson]]
 +
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
 
| <!-- Bootchart - my setup -->
 
| <!-- Bootchart - my setup -->
 
| <!-- Bootchart - desktop -->
 
| <!-- Bootchart - desktop -->

Revision as of 18:59, 17 February 2009

DATE TIME WHERE
Thu February 19, 2009 From 12:00 to 20:00 UTC (7am -> 3pm ET) #fedora-qa)

What to test?

Today's instalment of Fedora Test Day will focus on:

Who's available

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

  • Rawhide Fully updated (some tips below)
  • FAS Account - you can create an account in 3 minutes if you don't have one
  • Selinux enabled. If you need to run in permissive mode please file a bug against selinux
Warning.png
no animals will be hurt during testing

How to test?

1) update your machine to latest rawhide
   tip1: try F11 Alpha + updates if rawhide doesn't install
   tip2: install F10 + rawhide updates if F11 Alpha doesn't install on your machine
   tip3: yum-skipbroken may come in handy in case there are broken deps `yum --skipbroken update'
2) install bootchart
   `yum install bootchart'
3) Make sure the kernel you're about to boot has init set to bootchart.
   Open /boot/grub/menu.lst and check there's init=/sbin/bootchartd on the kernel command line
4) Reboot
5) Upload your hardware profile.
   Either via smoltSendProfile' in the terminal or smoltGui' for GUI. Don't forget to save a link to your profile 
   on the web. Also, your profile unique ID is saved in /etc/sysconfig/hw-uuid. Check the file contains your UUID.
6 optional) Run bootchart' on the command line.
   This should create bootchart.png image, which will show you the timings of your boot. Nice, isn't it? 
7) Upload your bootchart data (use upload link in the left menu) from /var/log/ along with your link to your profile.
   Use the table below. Create a unique copy of the file: 
   cp /var/log/bootchart.tgz ./Bootchart-head -n1 /etc/sysconfig/hw-uuid-myservices.tgz
   
8) Desktop setup: disable all services except those listed below, reboot, create new graph and 
   upload Bootchart-$UUID-desktop.tgz
   Enabled services (may need to install some using yum):
   tip: ntsysv' is your friend :)
NetworkManager, gacpid, atd, auditd, avahi-daemon, bluetooth, cpuspeed, crond, cups, gpm, haldaemon, ip6tables, iptables, irda, irqbalance, isdn, kerneloops, lm_sensors, mdmonitor, messagebus, microcode_ctl, netfs, nfslock, pcscd, portreserve, rpcbind, rpcgssd, rpcidmapd, rsyslog, sendmail, smolt, sshd, udev-post
9) Server setup: Enable only these services, reboot, and upload Bootchart-$UUID-server.tgz
acpid, atd, auditd, cpuspeed, crond, cups, gpm, haldaemon, httpd, ip6tables, iptables, irqbalance, lm_sensors, mdmonitor, messagebus, microcode_ctl,  mysqld, named, netfs, network, nfs, nfslock, nscd, ntpd, pcscd, portreserve, rpcbind, rpcgssd, rpcidmapd, rsyslog, sendmail, smartd, smolt, sshd, udev-post
10) Minimal service set: Enable only these services, reboot, and upload Bootchart-$UUID-minimal.tgz
atd,auditd,crond,haldaemon,messagebus,network,rsyslog,sshd

Now you're finished! Take a look into the bootcharts and identify bottlenecks. Use the notes section for simple notes, or services like http://www.pastebin.com if you want to add more information about your hardware. If you find any bugs, or have ideas how to improve the boot experiecen, file a bug into Red Hat Bugzilla.

The test day is divided into 2 parts - first part is about gathering the data. In the second part we're going to go through the data and prepare a report.

Results

User Smolt Profile Bootchart - my setup Bootchart - desktop Bootchart - server Bootchart - minimal Comments
User:SampleUser
David Kovalský HW
Adam Williamson HW

Advanced Test Plan

Various issues may affect the performance of boot, especially readahead and file system.

11) Install readahead, and for every setup (desktop, server, minimal) first boot for the first time, 
    let it gather it's data and then reboot with readahead on (chkconfig readahead on). Upload the bootchart
    into the same table with the name set to Bootchart-$UUID-server-ra.tgz (same for desktop and minimal)
12) Boot into a complete desktop with Firefox. You will need to 
    * patch bootchartd to wait for Firefox to start. Use this patch
    * enable desktop services
    * enable auto-login
    * start Firefox in the login script
    * reboot
    Again, provide bootchart data with and without readahead. Use Bootchart-$UUID-desktop-FF' (and optinally append 
    filesystem and readahead info)
13) Try installing with ext4 filesystem and XFS filesystem. Reboot, and upload bootchart data:
    Bootchart-$UUID-server-ra-xfs or Bootchart-$UUID-minimal-ext4.
14) Got an idea of what's affecting your system boot? Try it out and state so in the comments :)
15) Got a different system than Fedora Rawhide? We're interested in your results too! Use to table below:

Results (other distros)

User Smolt Profile Bootchart data Distro Enabled services Comments
User:SampleUser