On 06/21/2015 05:38 AM, Nicholas Nethercote wrote:
On Sat, Jun 20, 2015 at 1:36 PM, Aaron Klotz wrote:
I did some measurements last year at the 2014 JS workweek and it turns out
that the cost of converting the omnijar's JS source to jschars during
parsing is equivalent to the benefits we gain
On Mon, Jun 22, 2015 at 09:48:41AM -0700, Nicholas Alexander wrote:
> On Sat, Jun 20, 2015 at 10:01 PM, Gregory Szorc wrote:
>
> >
> >
> > > On Jun 20, 2015, at 20:55, Mike Hommey wrote:
> > >
> > >> On Sat, Jun 20, 2015 at 02:36:26PM -0600, Aaron Klotz wrote:
> > >>> On 6/20/2015 10:20 AM, Phil
On Sat, Jun 20, 2015 at 10:01 PM, Gregory Szorc wrote:
>
>
> > On Jun 20, 2015, at 20:55, Mike Hommey wrote:
> >
> >> On Sat, Jun 20, 2015 at 02:36:26PM -0600, Aaron Klotz wrote:
> >>> On 6/20/2015 10:20 AM, Philip Chee wrote:
> >>> Anyone want to try the same with Firefox nightly?
> >>
> >>
> >
> On Jun 20, 2015, at 20:55, Mike Hommey wrote:
>
>> On Sat, Jun 20, 2015 at 02:36:26PM -0600, Aaron Klotz wrote:
>>> On 6/20/2015 10:20 AM, Philip Chee wrote:
>>> Anyone want to try the same with Firefox nightly?
>>
>>
>> Already did it and subsequently filed bug 873638. We can do it if we m
On 2015-06-20 9:55 PM, Mike Hommey wrote:
Would encoding the js files in UTF-16 eliminate the conversion step? If
so, we can easily do that at packaging time, although local builds would
not benefit from that.
Mike
That is precisely what I had in mind.
_
On Sat, Jun 20, 2015 at 02:36:26PM -0600, Aaron Klotz wrote:
> On 6/20/2015 10:20 AM, Philip Chee wrote:
> >Anyone want to try the same with Firefox nightly?
> >
>
>
> Already did it and subsequently filed bug 873638. We can do it if we modify
> the encoding of the JS source at omnijar build time
On Sat, Jun 20, 2015 at 1:36 PM, Aaron Klotz wrote:
>
> I did some measurements last year at the 2014 JS workweek and it turns out
> that the cost of converting the omnijar's JS source to jschars during
> parsing is equivalent to the benefits we gain from StartupCache. Assuming
> that nothing has
On 6/20/2015 10:20 AM, Philip Chee wrote:
Anyone want to try the same with Firefox nightly?
Already did it and subsequently filed bug 873638. We can do it if we
modify the encoding of the JS source at omnijar build time.
I did some measurements last year at the 2014 JS workweek and it turn
I did a test and disabled the javascript precompile_cache. The SeaMonkey
ZIP build went from 45 133 376 bytes to 39 722 619 bytes. A saving of 5
410 757 bytes.
omni.ja went from 15 984 310 bytes to 10 444 677 bytes.
Subjectively first time cold start took a wee bit longer but in
subsequent startu
9 matches
Mail list logo