[QA] Release Meeting 2011-12-09

[Steve Langasek]

Hi Jean-Baptiste,

On Fri, Dec 09, 2011 at 09:34:43AM +0100, Jean-Baptiste Lallement wrote:
>  * Boot Speed testing
>    * Daily boot speed testing run on Desktop i386
>    * Report: http://reports.qa.ubuntu.com/reports/boot-speed/

Today's test for the Dell Vostro shows that ureadahead is not preloading
files as intended:

http://reports.qa.ubuntu.com/reports/boot-speed/dell-vostro-3400/2011-12-09_09-59-00/bootchart.png

This could be due to either a bug in ureadahead or a bug in the test
configuration.  (It does not appear to be caused by using an SSD; looking at
the device name listed in dmesg, this seems to be a rotational disk model. 
It would probably be helpful if this information were easily visible in some
sort of summary of the machine information.)

Is the methodology used for boot speed testing described somewhere?  I'd
like to try to reproduce this and figure out what's happening.  Not having
ureadahead working correctly causes a huge amount of noise in boot charts;
for instance, today's chart shows lightdm hitting the disk for a full second
before it gets around to starting X (which gets counted against the plumbing
budget), and this almost entirely accounts for the difference in plumbing
time in yesterday's run vs. today's on this machine.  There's no way to
tell from the currently available info if this is a regression in lightdm,
or just noise as a result of ureadahead not running correctly.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20111209/196c8094/attachment.pgp>