[opensuse-buildservice] Abysmal performance of buildservice
Hi: I thought it was a temporary problem, but it seems now there is a permanent performance problem on the OBS instance. Packages take hours even for getting scheduled and I have seen for example, kernel packages taking from several days to a week to be published. It is reaching to point where creating packages manually and publishing with a home-made script is faster and more efficient. If it is lacking of build-power ..ok..then some sort of build-quota should be put in place, or maybe putting all "home" repositories disabled by default requiring the user to enable build in a per-repo or per-package basis. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Monday, 11. July 2011, 15:40:46 schrieb Cristian Rodríguez:
Hi:
I thought it was a temporary problem, but it seems now there is a permanent performance problem on the OBS instance.
Packages take hours even for getting scheduled and I have seen for example, kernel packages taking from several days to a week to be published.
It is reaching to point where creating packages manually and publishing with a home-made script is faster and more efficient.
If it is lacking of build-power ..ok..then some sort of build-quota should be put in place, or maybe putting all "home" repositories disabled by default requiring the user to enable build in a per-repo or per-package basis.
we had idle build hosts less then a day ago. Also scheduler events were very low. So, without exact examples no one can explain the issues you describe. You are aware that publishing only happens when the entire repo has finished ? It does not matter when a single package has finished. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Jul 12, 2011 at 12:58 AM, Adrian Schröter
So, without exact examples no one can explain the issues you describe.
Go to this [1] project, and issue a rebuild of any package there. You'll see (if this problem is still happening) how it reaches the "finished" state and remains there for a lot more than what would be normal. [1] https://build.opensuse.org/project/monitor?project=home%3Aalina_q%3ANEPI -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 11. Juli 2011 schrieb Cristian Rodríguez:
Hi:
I thought it was a temporary problem, but it seems now there is a permanent performance problem on the OBS instance.
Packages take hours even for getting scheduled and I have seen for example, kernel packages taking from several days to a week to be
They are slow to be scheduled after you commit something? That can only happen when there are many other high prio events - and you can check yourself on /monitor. There are very seldom more than 30 of those. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Jul 12, 2011 at 9:24 AM, Stephan Kulow
They are slow to be scheduled after you commit something? That can only happen when there are many other high prio events - and you can check yourself on /monitor. There are very seldom more than 30 of those.
Yet I can confirm the slowness. It's just slow on scheduling, so even if you only have a few jobs showing in the /monitor, they take a lot to be processed. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Adrian Schröter -
Claudio Freire -
Cristian Rodríguez -
Stephan Kulow