Comment 35 for bug 1295732

CPU pinning and bigger hugepage size (1GB instead of 2MB) don't have a possitive impact on the boot times.

As a resume, big improvements can be achieve by:
- Using the virtio driver https://review.openstack.org/#/c/73837/
- Create the bm images compressed https://review.openstack.org/#/c/82772/
- Increase the specs of the seed vm (only has effect when the bm images are compressed) https://review.openstack.org/#/c/84078/
- Use a cirros image as an end user test https://review.openstack.org/#/c/83347/
- Make use of hugepages. (Should we offer this on the t-i story? Document it. Big improvement but not huge)
- Use of offline, mirrors, wheels.... (document it)

Small or partial improvements:
- Using tmpfs for the seed vm
- Using cpu=host-passthroug (need to test with newer CPUs)
- Increase bm vm specs
- Use of raw images for the seed

Future:
- Use of backing file for seed
- Perf. system during a full creation
    - Everything is sequencial (dib seed-boot seed-dib uc - boot uc - dib oc -boot-oc). Some phased can be parallelized
- Perf. inside the image boot process
- Robert's comments in https://bugs.launchpad.net/tripleo/+bug/1295732/comments/3
- ??? more ideas???