Rob noted that the ramdisk build seems incredibly slow in Stephen's original numbers (632s, see comment #7)
Some data:
on the lab hardware, calling diskimage-builder directly, for amd64, with --offline:
* 2m40s http_proxy set, elements set to "ubuntu deploy apt-sources apt-conf" (note: second run of this dropped to 1m21s)
* 3m53s http_proxy set, elements set to "ubuntu deploy"
* 4m17s no http_proxy set, elements set to "ubuntu deploy"
* 12m16s http_proxy set, elements set to "ubuntu deploy", pre-cached cloud image removed first
calling devtest_ramdisk.sh with the best case options from above (i.e. http_proxy, apt-sources/apt-conf) gave a run of 1m41s.
Stephen: is that 10 minute ramdisk build consistent? I'm wondering if some $NODE_DIST or $DIB_COMMON_ELEMENTS setting is causing an unnecessary amount of building work to be happening, but it's also possible that this was just a fresh ubuntu cloud image being downloaded.
Rob noted that the ramdisk build seems incredibly slow in Stephen's original numbers (632s, see comment #7)
Some data:
on the lab hardware, calling diskimage-builder directly, for amd64, with --offline:
* 2m40s http_proxy set, elements set to "ubuntu deploy apt-sources apt-conf" (note: second run of this dropped to 1m21s)
* 3m53s http_proxy set, elements set to "ubuntu deploy"
* 4m17s no http_proxy set, elements set to "ubuntu deploy"
* 12m16s http_proxy set, elements set to "ubuntu deploy", pre-cached cloud image removed first
calling devtest_ramdisk.sh with the best case options from above (i.e. http_proxy, apt-sources/ apt-conf) gave a run of 1m41s.
Stephen: is that 10 minute ramdisk build consistent? I'm wondering if some $NODE_DIST or $DIB_COMMON_ ELEMENTS setting is causing an unnecessary amount of building work to be happening, but it's also possible that this was just a fresh ubuntu cloud image being downloaded.