> > Said that, I now have the fork() patch in all my trees and enjoy 50% faster
> > WPA times.  I changed my mind about claim that stremaing should be disk 
> > bound -
> > it is hard to hope for disk boundness for something that should fit in 
> > cache.
> 
> It should at least limit its fork rate according to -flto=N or jobserver.
It limits forks to -flto=N.
If the patch seems resonable, I will look into posiblity of adding my jobserver 
client
based on GNU make code.

I also think with -flto we want wrapper to figure out number of threads and 
suppy
default =N (i.e. nonparallel lto would be -flto=0).  Most people don't want to 
worry
about =n/=jobserv parameters and those few projects that don't want to start 
too many
processes to not explode in memory use can get their build machinery right.

Honza
> 
> > We went down from 5GB to 2GB of streaming for Firefox that is good.  But we 
> > will
> > see again 4GB once Martin's code layout work will land.  I think it is from 
> > good
> > part because of the origin fun above.
> 
> Ugh.
> 
> Richard.

Reply via email to