DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29248>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29248 ------- Additional Comments From [EMAIL PROTECTED] 2004-12-11 03:51 ------- It is not the problem of computing the dependencies - that is a solved problem :topological sort of the targets, based on target dependencies and dependencies order within a "depends". There are two optimizations that can (and should be implemented): - add a "depends-without-regard-to-order" attribute that means the dependencies need not be executed in the stated order - add a properties file that records some metric of cost for each target, so the optimizer can achieve better results by solving a static scheduling optimization problem (*) ------ (*) Example: let's say we have the following targets - A and B take 5 minutes - C and D take 1 minute - no dependencies between them If you know the duration (and by the third build you do) and you comunicate that to the scheduler, it might schedule (A || B) then (C || D) and be done in 6 minutes on a 2-CPU machine, while a naive random scheduler might schedule A on CPU0 for 5 min, then C, D and B on CPU1 for 7 total minutes. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
