On 19 Nov 2002, Jonas Jensen <[EMAIL PROTECTED]> wrote: > > This patch is a solution to send more than one job at each > > CPU. But the solution should go beyond that. I think that the > > dispatch should be completely dynamic. I see our dev environment > > being composed of dev machines for developpers and compile farms > > to speedup the compilation. These machines should be loaded with > > compilation from all the developers at the same time, when they > > run compilation. But then, the spawned jobs should be sent > > depending on the current load of each compilation server. This > > could be achieved if the server send an average of its load > > before/after each compilation sent. How hard would it be to > > modify the distcc code so the server send the client the laodavg?
I do plan to improve the scheduler so that it can take into account faster machines, SMP machines, and work arriving from different clients. However for the reasons in the FAQ I don't think sending the load average to the client or to a central controller is a good approach. -- Martin _______________________________________________ distcc mailing list [EMAIL PROTECTED] http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
