Is this the correct bug report for this issue? On my quite new laptop (dualcore 2.2 GHz AMD CPU, 3 GiB of RAM, a 320 GB HDD), sreadahead consistently slows startup down by about 5.5 seconds.
I measured this with the following job:
start on login-session-start
task
script
cat /proc/uptime >>/uptimes
if [ "$(wc -l /uptimes | cut -d' ' -f1)" -lt 5 ]; then
reboot
fi
end script
The average measured time with sreadahead disabled is 33.07 s, and with sreadahead enabled, 38.55 s.
Could something as simple as making the rest of the startup wait for sreadahead to finish fix this? The problem might simply be caused by thrashing when sreadahead is doing its thing simultaneously with the rest of the system booting.
Is this the correct bug report for this issue? On my quite new laptop (dualcore 2.2 GHz AMD CPU, 3 GiB of RAM, a 320 GB HDD), sreadahead consistently slows startup down by about 5.5 seconds.
I measured this with the following job:
start on login-session-start
task
script
cat /proc/uptime >>/uptimes
if [ "$(wc -l /uptimes | cut -d' ' -f1)" -lt 5 ]; then
reboot
fi
end script
The average measured time with sreadahead disabled is 33.07 s, and with sreadahead enabled, 38.55 s.
Could something as simple as making the rest of the startup wait for sreadahead to finish fix this? The problem might simply be caused by thrashing when sreadahead is doing its thing simultaneously with the rest of the system booting.