| 2012-05-17 13:05:08 |
Scott Moser |
description |
cloud-init coudl re-enable ureadahead if it is actually running on real-hardware.
Related bugs:
* bug 499520: default uec-image requires at least 300 M of RAM to run - m1.small and c1.medium not needed by default |
Since bug 499520, cloud-init currently disables ureadahead by using a dpkg-divert of /etc/upstart/ureadahead.conf. The reasoning behind this was that:
a.) ureadahead was causing OOM on boot small vms (~ 300M)
b.) ureadahead inside a VM doesn't generally make any sense. Ureadahead tries to optimize disk reads for ssd or spinning disks. Its methods of determining if the disk of the system is ssd or spinning won't work in a VM.
c.) ureadahead is part of ubuntu-minimal task, and we did not want to change that.
Recently, though, we've started using cloud-init on real hardware, where ureadahead could be of use.
Thus, I'd like to have a better solution. I think ureadahead would ideally disable itself if it found one of the following conditions:
1 small amount of memory (<512 or even 1024M)
2 if it is running in a container
3 no definitive knowledge of the type of disks used (if it thought this might be a VM)
Of those options, determining the first 2 are straight forward, and I would think could be done in the upstart job even. I'm not familiar enough with ureadahead to know how easily it would be to determine number 3.
Related bugs:
* bug 499520: default uec-image requires at least 300 M of RAM to run - m1.small and c1.medium not needed by default |
|
