I've been experiencing slow boot on an old laptop and this is the result of my "fix" research;
Laptop: HP pavilion, 512MB ram, single processor
OS: Kubuntu 14.04.2 up-to-date as of this date
Symptoms: Boot operation is periodically slowed by the process "update-apt-xapi", the name for which is truncated from "update-apt-xapian-index".
Using either the system monitor gui or "top" in Konsole, the culprit was the above mentioned process, which was taking all available processor cycles, causing a total of 100% CPU usage and causing all other processes to stop/delay for up to 15 minutes.
Solution: Web search found this link, the instructions work ON_MY_MACHINE, so your mileage may vary.
http://vk5hse.blogspot.com/2014/08/ubuntu-apt-xapian-index-update-manager.html
Note that the solution invovles installing the "cpulimit" tool and editing a file in the /etc/cron.weekly directory. Not hard to implement.
This works for me and if your situation is similar, it may work for you.
This problem only appears when you have a resource-poor system, such as this one. You may not notice it on a multi-processor system with lots of ram. I only found it after I installed 14.04 LTS on a laptop.
Also, this has been a reported problem since at least 2010 and I'm not sure it has been fixed in newer versions...
FYI
Laptop: HP pavilion, 512MB ram, single processor
OS: Kubuntu 14.04.2 up-to-date as of this date
Symptoms: Boot operation is periodically slowed by the process "update-apt-xapi", the name for which is truncated from "update-apt-xapian-index".
Using either the system monitor gui or "top" in Konsole, the culprit was the above mentioned process, which was taking all available processor cycles, causing a total of 100% CPU usage and causing all other processes to stop/delay for up to 15 minutes.
Solution: Web search found this link, the instructions work ON_MY_MACHINE, so your mileage may vary.
http://vk5hse.blogspot.com/2014/08/ubuntu-apt-xapian-index-update-manager.html
Note that the solution invovles installing the "cpulimit" tool and editing a file in the /etc/cron.weekly directory. Not hard to implement.
This works for me and if your situation is similar, it may work for you.
This problem only appears when you have a resource-poor system, such as this one. You may not notice it on a multi-processor system with lots of ram. I only found it after I installed 14.04 LTS on a laptop.
Also, this has been a reported problem since at least 2010 and I'm not sure it has been fixed in newer versions...
FYI
Comment