[opensuse-factory] Some rebuild statistics
Hi, http://www.suse.de/~coolo/factory/ shows some statistics about the rebuildtime of factory. You can see in the graph how many packages can build in parallel and how many are waiting for others to finish. As you can see, half the rebuild time we wait for OpenOffice - but note that this is not really true in practise as the real rebuild time is not dominated by the time OpenOffice builds, but by the time the many packages that _could_ build in parallel are build in the workers we have. So even if we could rebuild all packages with unlimited workers in 24 hours, in reality it takes at least 48 hours (which is the reason we usually only do it friday to sunday). The longest path worries me a lot though, but I have no good idea how to avoid e.g. swig being behind mysql. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 15 May 2010 08:16:02 +0200, Stephan Kulow <coolo@novell.com> wrote:
Hi,
http://www.suse.de/~coolo/factory/ shows some statistics about the rebuildtime of factory. You can see in the graph how many packages can build in parallel and how many are waiting for others to finish.
As you can see, half the rebuild time we wait for OpenOffice - but note that this is not really true in practise as the real rebuild time is not dominated by the time OpenOffice builds, but by the time the many packages that _could_ build in parallel are build in the workers we have.
So even if we could rebuild all packages with unlimited workers in 24 hours, in reality it takes at least 48 hours (which is the reason we usually only do it friday to sunday).
The longest path worries me a lot though, but I have no good idea how to avoid e.g. swig being behind mysql.
Greetings, Stephan
- Could the packages with no dependancies at all be directed to any idle work queues (if available) - Is there something that finds the first package in a long dependancy queue [e.g oo] gets a high pritority to build next or findle a idle que to build on ? just my 20c worth Glenn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stephan Kulow wrote:
The longest path worries me a lot though, but I have no good idea how to avoid e.g. swig being behind mysql.
Maybe swig could be eliminated in that path. Looks like lcms needs it for it's python bindings only. By building the python bindings in a separate spec file lcms itself wouldn't depend on swig anymore. I also wonder why graphviz depends on ksh and bind on mysql. Maybe bind could be modified to build the database drivers separately. Alternatively a minimal bind package with reduced dependencies could be created that is used for building only. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Montag 17 Mai 2010 schrieb Ludwig Nussel:
Stephan Kulow wrote:
The longest path worries me a lot though, but I have no good idea how to avoid e.g. swig being behind mysql.
Maybe swig could be eliminated in that path. Looks like lcms needs it for it's python bindings only. By building the python bindings in a separate spec file lcms itself wouldn't depend on swig anymore. I also wonder why graphviz depends on ksh and bind on mysql. Maybe bind could be modified to build the database drivers separately. Alternatively a minimal bind package with reduced dependencies could be created that is used for building only.
The swig:lcms one is indeed also the one I'm targeting first. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Montag 17 Mai 2010 schrieb Stephan Kulow:
Am Montag 17 Mai 2010 schrieb Ludwig Nussel:
Stephan Kulow wrote:
The longest path worries me a lot though, but I have no good idea how to avoid e.g. swig being behind mysql.
Maybe swig could be eliminated in that path. Looks like lcms needs it for it's python bindings only. By building the python bindings in a separate spec file lcms itself wouldn't depend on swig anymore. I also wonder why graphviz depends on ksh and bind on mysql. Maybe bind could be modified to build the database drivers separately. Alternatively a minimal bind package with reduced dependencies could be created that is used for building only.
The swig:lcms one is indeed also the one I'm targeting first.
Ludwig and me made quite some progress and not only did we save 6 hours, we also made the non-Ooo part much shorter: http://www.suse.de/~coolo/factory/ So we could rebuild the whole distro beside OpenOffice_org in < 9 hours, but take another 10 to get a FTP tree out with OpenOffice_org - this is something we may need to work on, even though I'm not sure how. I don't really want to ban Ooo out of factory. But for the current rebuild I disabled OOo, so we get a FTP tree with fixed gcc quickly and once we have it, I'll reenable Ooo. And perhaps this we need to somehow automate. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, 31 May 2010, Stephan Kulow wrote:
Ludwig and me made quite some progress and not only did we save 6 hours, we also made the non-Ooo part much shorter:
Impressive -- congrats! Gerald -- Dr. Gerald Pfeifer gp@novell.com | SUSE Linux Products GmbH Director Product Management | HRB 16746 (AG Nuremberg) SUSE Linux Enterprise, openSUSE, Appliances | GF Markus Rex -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
doiggl＠velocitynet.com.au -
Gerald Pfeifer -
Ludwig Nussel -
Stephan Kulow