Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here is my bootchart (WARNING! Huge image!)

Here is my kernel log

Here is my syslog

Here is my dmesg

share|improve this question

Suspend to RAM, and wake up.

Use a electricity measuring tool, to estimate the cost of, for example, one year of such behaviour. If it is acceptable, I guess no other method will beat it. If it is not acceptable, you have to name tradeoffs and prices you're willing to pay (for SSD - not for me ;) ).

share|improve this answer
yes, although I would prefer hibernation since it's more similar to shutting down. But then again, that requires disk I/O too :) – steabert Jan 16 '12 at 14:01

Considering your boot time is mainly consumed by disk I/O, I would guess buying a faster disk would help a lot, e.g. 7200 rpm or SSD.

share|improve this answer

Providing enough space for swap may reduce the boot time

share|improve this answer
How to do this? (I recommend expanding this answer.) – Eliah Kagan Jan 21 '13 at 7:10

Installing preload Install preload helped me. Can be found in the Software Center.

share|improve this answer

Have you tried using all cores with CONCURRENCY setting to shell? Not sure if has any effect when waking up from suspended state. For startup, removing items like ubuntu one and others made a little difference for me. Disabling visual effects also does some good with kompiz taking lesser cpu. All of these and others consolidated here -

share|improve this answer
CONCURRENCY=shell is now deprecated. See the comments at the top of /etc/init.d/rc. It actually defaults to the best possible value now. – Caesium Jan 17 '12 at 1:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.