On 2010-03-21 11:07 , Ryan Schmidt wrote: > Do you suppose it would be nice to use setpriority in other phases as > well? There are some ports that, though perhaps they shouldn't, > compile in either the configure or destroot phases; perhaps they > should use lower priority then too. Even ports that don't do this > will sometimes do a lot of work in the configure phase, which can eat > into CPU time.
configure and destroot phases in general are I/O bound and not very CPU intensive. Changing the scheduling priority only helps to reduce CPU load, I/O is not affected. Although there might be ports doing some heavy stuff in configure/destroot it usually does not take that long that it would disturb normal operations at the same time. But if we want to lower priority, we would only have to add configure.nice/destroot.nice options to portconfigure/portdestroot. Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
