Second status update:
The numbers from disabling PGO on image, accessible and webrtc are in, and
the linker max vmem size is down by only ~200MB, which is quite
disappointing, especially since according to Randell, putting webrtc
outside of libxul should buy us something around 600MB...
So, as de
Status update: we have landed three patches on mozilla-inbound which
disable PGO on the following directories (rdf/, image/ and accessible/)
and I have triggered PGO builds on top of them to see how much they can
shave off of the linker's vmem usage. Randel is also working on taking
some webrt
On Mon, Jan 21, 2013 at 10:56:28PM +0100, Mike Hommey wrote:
> On Tue, Jan 22, 2013 at 10:52:39AM +1300, Robert O'Callahan wrote:
> > Exactly what control do we have over what gets PGOed? In particular:
> >
> > 1) Are we able to exclude particular object files or libraries from PGO
> > when we lin
On Mon, Jan 21, 2013 at 1:52 PM, Robert O'Callahan wrote:
> Exactly what control do we have over what gets PGOed? In particular:
>
> 1) Are we able to exclude particular object files or libraries from PGO
> when we link libxul, reducing PGO memory usage for the final link? I think
> you said "yes"
On Tue, Jan 22, 2013 at 10:52:39AM +1300, Robert O'Callahan wrote:
> Exactly what control do we have over what gets PGOed? In particular:
>
> 1) Are we able to exclude particular object files or libraries from PGO
> when we link libxul, reducing PGO memory usage for the final link? I think
> you s
Exactly what control do we have over what gets PGOed? In particular:
1) Are we able to exclude particular object files or libraries from PGO
when we link libxul, reducing PGO memory usage for the final link? I think
you said "yes" on IRC.
2) Are we able to collect a set of object files, link them
On 21/01/2013 21:47, Ehsan Akhgari wrote:
1. mozilla-central/inbound will remain closed to all check-ins except
the ones that do not add any code which gets linked into libxul on Windows.
Both inbound and central are APPROVAL REQUIRED as of now, any patches
that don't touch libxul can land wit
This week's MemShrink meeting will be brought to you by this awesome bug fix:
https://bugzilla.mozilla.org/show_bug.cgi?id=795988
Note:
* New meeting/vidyo room (this week only)
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprior
I'm sorry that I have to be the bearer of bad news about our trees, but
we have finally started to hit the linker maximum memory size when
linking libxul as part of our Windows PGO builds, and as a result,
mozilla-central and inbound are CLOSED for now.
I propose the following:
1. mozilla-cen
On Thursday, September 20, 2012 3:59:59 PM UTC+2, Estanislao Gonzalez wrote:
> Am Donnerstag, den 20.09.2012, 09:29 -0400 schrieb Benjamin Smedberg:
>
> > On 9/20/2012 9:14 AM, Estanislao Gonzalez wrote:
>
> > > Hi,
>
> > >
>
> > > This is probably nothing... but I was testing something else a
W3C is proposing a charter for a new Web Speech Working Group.
For more details, see:
http://lists.w3.org/Archives/Public/public-new-work/2013Jan/0003.html
http://www.w3.org/2012/12/speech-charter.html
Mozilla has the opportunity to send comments or objections through
Thursday, February 28. Pleas
11 matches
Mail list logo
