| 2012-02-03 16:10:43 |
Scott Moser |
bug |
|
|
added bug |
| 2012-02-03 16:10:43 |
Scott Moser |
attachment added |
|
data collected from each of the 8 instances i ran. https://bugs.launchpad.net/bugs/926160/+attachment/2710789/+files/data-collected.tar.gz |
|
| 2012-02-03 16:11:20 |
Scott Moser |
bug |
|
|
added subscriber Ubuntu Server Release Tracking |
| 2012-02-03 16:12:01 |
Scott Moser |
description |
See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase.
This compares what I found on
ubuntu-oneiric-11.10-<arch>-server-20120108
ubuntu-precise-daily-<arch>-server-20120202
The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows:
-------------- | 11.10 | prec | %growth
amd64 disk.img | 218M | 228M | 4.8
amd64 .tar.gz | 207M | 217M | 4.6
amd64 ebs df | 762M | 973M | 27.6
amd64 inst df | 655M | 823M | 25.6
i386_ disk.img | 198M | 210M | 6.0
i386_ .tar.gz | 188M | 200M | 6.3
i386_ ebs df | 689M | 814M | 18.1
i386_ inst df | 582M | 753M | 29.3
(Note, precise df numers are from daily build 20120108, 1 day after alpha2)
I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem).
So i have the following separate issues raised from above:
* why such a dramatic growth between 11.10 and 12.04 current
* can we/should we get the EBS filesystem usage more in line with instance-store?
* Why the vast outlier below in increased usage of ebs for a given release-arch:
oneiric-amd64: 16%
oneiric-i386: 18%
precise-amd64: 18%
precise-i386: 8% |
See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase.
This compares what I found on
ubuntu-oneiric-11.10-<arch>-server-20120108
ubuntu-precise-daily-<arch>-server-20120202
The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows:
-------------- | 11.10 | prec | %growth
amd64 disk.img | 218M | 228M | 4.8
amd64 .tar.gz_ | 207M | 217M | 4.6
amd64 ebs df__ | 762M | 973M | 27.6
amd64 inst df_ | 655M | 823M | 25.6
i386_ disk.img | 198M | 210M | 6.0
i386_ .tar.gz_ | 188M | 200M | 6.3
i386_ ebs df__ | 689M | 814M | 18.1
i386_ inst df_ | 582M | 753M | 29.3
(Note, precise df numers are from daily build 20120108, 1 day after alpha2)
I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem).
So i have the following separate issues raised from above:
* why such a dramatic growth between 11.10 and 12.04 current
* can we/should we get the EBS filesystem usage more in line with instance-store?
* Why the vast outlier below in increased usage of ebs for a given release-arch:
oneiric-amd64: 16%
oneiric-i386: 18%
precise-amd64: 18%
precise-i386: 8% |
|
| 2012-02-03 16:27:07 |
Scott Moser |
description |
See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase.
This compares what I found on
ubuntu-oneiric-11.10-<arch>-server-20120108
ubuntu-precise-daily-<arch>-server-20120202
The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows:
-------------- | 11.10 | prec | %growth
amd64 disk.img | 218M | 228M | 4.8
amd64 .tar.gz_ | 207M | 217M | 4.6
amd64 ebs df__ | 762M | 973M | 27.6
amd64 inst df_ | 655M | 823M | 25.6
i386_ disk.img | 198M | 210M | 6.0
i386_ .tar.gz_ | 188M | 200M | 6.3
i386_ ebs df__ | 689M | 814M | 18.1
i386_ inst df_ | 582M | 753M | 29.3
(Note, precise df numers are from daily build 20120108, 1 day after alpha2)
I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem).
So i have the following separate issues raised from above:
* why such a dramatic growth between 11.10 and 12.04 current
* can we/should we get the EBS filesystem usage more in line with instance-store?
* Why the vast outlier below in increased usage of ebs for a given release-arch:
oneiric-amd64: 16%
oneiric-i386: 18%
precise-amd64: 18%
precise-i386: 8% |
See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase.
This compares what I found on
ubuntu-oneiric-11.10-<arch>-server-20120108
ubuntu-precise-daily-<arch>-server-20120202
The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows:
-------------- | 11.10 | prec | %growth
amd64 disk.img | 218M | 228M | 4.8
amd64 .tar.gz_ | 207M | 217M | 4.6
amd64 ebs df__ | 762M | 883M | 15.8
amd64 inst df_ | 655M | 823M | 25.6
i386_ disk.img | 198M | 210M | 6.0
i386_ .tar.gz_ | 188M | 200M | 6.3
i386_ ebs df__ | 689M | 814M | 18.1
i386_ inst df_ | 582M | 753M | 29.3
(Note, precise df numers are from daily build 20120108, 1 day after alpha2)
I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem).
So i have the following separate issues raised from above:
* why such a dramatic growth between 11.10 and 12.04 current
* can we/should we get the EBS filesystem usage more in line with instance-store?
* Why the change in increased usage of ebs for a given release-arch:
oneiric-amd64: 16%
oneiric-i386: 18%
precise-amd64: 7.2%
precise-i386: 8% |
|
| 2012-02-03 16:28:32 |
Scott Moser |
attachment added |
|
fixed data collected https://bugs.launchpad.net/ubuntu/+bug/926160/+attachment/2710853/+files/data-collected.tar.gz |
|
| 2012-02-03 17:06:24 |
Scott Moser |
description |
See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase.
This compares what I found on
ubuntu-oneiric-11.10-<arch>-server-20120108
ubuntu-precise-daily-<arch>-server-20120202
The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows:
-------------- | 11.10 | prec | %growth
amd64 disk.img | 218M | 228M | 4.8
amd64 .tar.gz_ | 207M | 217M | 4.6
amd64 ebs df__ | 762M | 883M | 15.8
amd64 inst df_ | 655M | 823M | 25.6
i386_ disk.img | 198M | 210M | 6.0
i386_ .tar.gz_ | 188M | 200M | 6.3
i386_ ebs df__ | 689M | 814M | 18.1
i386_ inst df_ | 582M | 753M | 29.3
(Note, precise df numers are from daily build 20120108, 1 day after alpha2)
I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem).
So i have the following separate issues raised from above:
* why such a dramatic growth between 11.10 and 12.04 current
* can we/should we get the EBS filesystem usage more in line with instance-store?
* Why the change in increased usage of ebs for a given release-arch:
oneiric-amd64: 16%
oneiric-i386: 18%
precise-amd64: 7.2%
precise-i386: 8% |
See below for detail, but basically from oneiric released images to precise images, we've grown from root filesystem used of 762M to 973M. That is 27% size increase.
This compares what I found on
ubuntu-oneiric-11.10-<arch>-server-20120108
ubuntu-precise-daily-<arch>-server-20120202
The .img and .tar.gz files on cloud-images have grown also, but strangely it seems less. comparing alpha-2 from precise to last release of oneiric (20120108) shows:
-------------- | 11.10 | prec | %growth
amd64 disk.img | 218M | 228M | 4.8
amd64 .tar.gz_ | 207M | 217M | 4.6
amd64 file tot | 559M | 575M | 2.9
amd64 ebs df__ | 762M | 883M | 15.8
amd64 inst df_ | 655M | 823M | 25.6
i386_ disk.img | 198M | 210M | 6.0
i386_ .tar.gz_ | 188M | 200M | 6.3
i386_ file tot | 484M | 505M | 4.3
i386_ ebs df__ | 689M | 814M | 18.1
i386_ inst df_ | 582M | 753M | 29.3
(Note, precise df numers are from daily build 20120108, 1 day after alpha2)
'file tot' is result of 'du --total --one-file-system --apparent-size'.
I suspect that part of the discrepancy between instance and ebs is somehow related to how we populate them. In the build process, the instance store builds are done into a 1.4G filesystem, and then that is grown (resize2fs) to 10G before publishing to EC2. The EBS population script downloads the 1.4GB filesystem image, creates a filesystem on a 8G disk, then mounts it loopback and rsync's the data from the image to the new filesystem. (Essentially, mkfs is done on a 1.4G filesystem, and one is done on a 8G filesystem).
So i have the following separate issues raised from above:
* why such a dramatic growth between 11.10 and 12.04 current
* can we/should we get the EBS filesystem usage more in line with instance-store?
* Why the change in increased usage of ebs for a given release-arch:
oneiric-amd64: 16%
oneiric-i386: 18%
precise-amd64: 7.2%
precise-i386: 8% |
|
| 2012-02-07 16:42:01 |
Scott Moser |
ubuntu: assignee |
Ubuntu Server Team (ubuntu-server) |
Ben Howard (utlemming) |
|
| 2012-02-28 15:14:54 |
Ben Howard |
ubuntu: importance |
Medium |
Wishlist |
|
| 2012-02-28 15:22:53 |
Ben Howard |
ubuntu: status |
Confirmed |
Won't Fix |
|
| 2016-07-16 00:40:47 |
Mathew Hodson |
affects |
ubuntu |
cloud-images |
|
