Hey there LowEndTalk,
Just wanted to get a quick consensus on if the following is acceptable:
[root@s1.example.com ~]# python ps_mem.py
Private + Shared = RAM used Program
320.0 KiB + 79.5 KiB = 399.5 KiB auditd
656.0 KiB + 98.5 KiB = 754.5 KiB crond
492.0 KiB + 279.0 KiB = 771.0 KiB mingetty (6)
728.0 KiB + 127.0 KiB = 855.0 KiB init
264.0 KiB + 689.5 KiB = 953.5 KiB udevd (2)
952.0 KiB + 106.5 KiB = 1.0 MiB rsyslogd
1.1 MiB + 115.5 KiB = 1.2 MiB bash
2.9 MiB + 908.5 KiB = 3.8 MiB sshd (2)
---------------------------------
9.8 MiB
=================================
[root@s1.example.com ~]# free -m
total used free shared buffers cached
Mem: 238 51 186 0 2 14
-/+ buffers/cache: 34 204
Swap: 0 0 0
[root@s1.example.com ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-LogVol00
4.7G 761M 3.7G 17% /
/dev/vda1 248M 33M 203M 14% /boot
[root@s1.example.com ~]# ioping -c10 /boot ... --- /boot (ext4 /dev/vda1) ioping statistics --- 10 requests completed in 9.0 s, 208.3 k iops, 813.8 MiB/s min/avg/max/mdev = 3 us / 4 us / 5 us / 0 us
[root@s1.example.com ~]# ioping -c10 /boot -s 64k ... --- /boot (ext4 /dev/vda1) ioping statistics --- 10 requests completed in 9.0 s, 44.2 k iops, 2.7 GiB/s min/avg/max/mdev = 17 us / 22 us / 25 us / 2 us
We are preparing another round of completely up-to-date templates for all of our Linux Operating Systems (and maybe even for some other OSes, we're not quite sure yet.) The above is the output of various commands from our os-linux_centos_6.5-x86_64 template, which is not meant to be minimal by any means, having the following base packages:
http://pastie.org/private/u2bul9loty8qtiyqm95sg
So the question is, what can we remove to further improve the image? What optimizations would you like to see put in place by default on the image that would not already be there from the Minimal installation (via a normal media for example.)
We have applied the RedHat recommended tuned profiles, as well as various tweaks optimized for 10Gbps internal links and use with VirtIO networking and storage, but are a bit stumped as to how we could further optimization the images.
We will be releasing the template, as well as full instructions as to how we get it to here, in our Provider Template Database which we plan to release later this month. Specifically designed for providers to have stable and up to date templates from which to provide their customers services, or to distill their own appliances from. As well, the PTD is great for consumers and end-user customers as well, as they can pick and choose appliances to use with any provider that allows you to upload your own templates or ISO installation media.
EDIT: The template's current sealed size is 255.98M , and contains contextualization scripts to support any host environment's contextualization engine / metadata provider (including cloud-init and OpenNebula's one-context scripts.)