While 1,000 is an arbitrary number, kudos to Allon for his 1,000 patch
to ovirt-engine repo being merged!
(yes, a lot of these are cleanup patches, but these matter too).
 you can use 'git shortlog -sn' to get the full list.
> ----- Forwarded Message -----
>> From: "Liran Zelkha" <liran.zelkha(a)gmail.com>
>> To: "engine-devel" <engine-devel(a)ovirt.org>
>> Cc: "Itamar Heim" <iheim(a)redhat.com>, "Barak Azulay" <bazulay(a)redhat.com>, "Allon Mureinik" <amureini(a)redhat.com>
>> Sent: Wednesday, July 3, 2013 1:08:08 PM
>> Subject: BatchUpdates and VdsUpdateRuntimeInfo
>> Hi all,
>> Batch updates are now merged, so please start using it. As usage example,
>> please check VdsUpdateRuntimeInfo code. Attached doc shows performance
>> benefits from using batch over regular update.
> <Batch Updates in VdsUpdateRuntimeInfo.pdf>
Is the percentage per each VM update? Or a loaded "average" system?
due to multiple errors lately with the jenkins jobs that runs per patch on gerrit patches for engine,
infra team has disabled the job for now and enabled a basic compilation job instead. 
this is caused by a slow jenkins slave that doesn't have the capacity to handle the load of patches.
we're working hard on adding new and powerful jenkins slaves soon and hopefully by next week we can start using them.
for now, if you have a patch that has -1 from the 'gerrit findbugs' job you can:
1. contact gerrit admin (dcaro) to remove the jenkins user from that patch
2. if you'll send a new patchset, it will be removed automaticly.
3. contact infra(a)ovirt.org if need help/info
sorry for the noise, hopefully we'll be able to enable it back soon with newer infra.
oVirt infra team.
Recently I merged the os info  patches. Its main responsibility is to
make our OS-bounded configuration file-based
rather than combination of hard-coded enum (VmOsType) and db config values.
What is there to configure?
* available OS types - what you see in the drop-down selection for the os
e.g os.RHEL6.name = Red Hat Enterprise Linux 6
* recommended min/max memory per os
os.Unassigned.resources.maximum.ram.value = 64000
* supported network devices - this will actually set the drop-down of
nic types in new Interface dialog
os.Windows7.devices.network.value = rtl8139_pv, rtl8139, e1000, pv
* compat version values
os.Fedora12.devices.audio.value = ich6
os.Fedora12.devices.audio.value.3.2 = ac97
* inheritance - DRY :)
os.RHEL5.derivedFrom.value = RHEL4
os.RHEL4.family = linux
* cpu Arch - currently we support only x86 but this will come handy for
supporting powerPC arch or arm etc after cross-matching with the cluster
os.Other.cpuArchetecture.value = x86
The file is located at
/etc/ovirt-engine/osinfo.conf.d/00-osinfo-defaults.properties and is
symlinked to /usr/share/ovirt-engine/conf/osinfo-defaults.properties
If you want to overide the values or just add your setup more OSs just
add 10-osinfo.properties under osinfo.conf.d
Bare in mind, If you ever have to add logic against OSs pls don't add it
to vdc_options. Use the osinfo instead. Cleanups from
ConfigValues and vdc_options will soon follow as well as treatment for
custom icon images for OSs.