On Tue, Apr 09, 2013 at 12:25:15AM +0200, Jan Engelhardt wrote:
On Monday 2013-04-08 13:05, Jos Poortvliet wrote:
Our binary delivery server is also getting full and that, too, will need a solution. Cleaning up only gets us so far. Help finding a new server is welcome, Adrian can probably tell you what we need if you ask.
With respect to multi-threading, the source code could use improvements in some places. I have seen bs_srcserver using multiple processes (at least something!) at times,
You're kidding, right? The source server is a web server, it'll spawn a new process for every request.
but that does not seem to be the case for bs_repserver or bs_sched. Especially the scheduler would benefit from it in cases where #cores >> #architectures to schedule for.
That depends on if it's IO bound or CPU bound. If it's CPU bound, another option is to improve the code. We already do some of the heavy work in an XS module, be might want to move some other stuff there as well. In most of the cases it seems to be IO bound, though. Note also that the current version of the scheduler supports async src server requests, we might want to try that for OBS. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org