On 2013-01-30 11:40 PM, Robert O'Callahan wrote:
On Thu, Jan 31, 2013 at 5:34 PM, Ehsan Akhgari <[email protected] <mailto:[email protected]>> wrote:On 2013-01-30 11:11 PM, Robert O'Callahan wrote: What about leaving PGO/LTCG enabled for a subset of our modules? Is that not a possible solution? I did in fact measure that by disabling PGO/LTCG on all directories except content, dom, layout and xpcom. I can't seem to find the try push right now (and bug 836626 doesn't help), but IIRC that bought us 600MB-700MB. To put that number in context, we have increased the linker memory usage by about 1GB over the past 10 months. Therefore, this will fall under option #2. Can we do it at finer granularity than that? There's a lot under content and dom that aren't critical.
Sure, that is definitely an option. Note that I have already turned off PGO/LTCG for things like mathml and svg under content, dom and layout (see the dependencies of bug 832992).
Also, reducing the number of directories that are PGO/LTCG should mean that the rate of growth decreases proportionally. Even more than proportionally, if we flip our default for entirely new modules to be non-PGO/LTCG, as I assume we would.
The decrease is unfortunately not linear, as it seems like the big memory eater is LTCG, and unfortunately we cannot opt out of that if we want to do any PGO.
Cheers, Ehsan _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
