The concerns that I have is that the start-up cache proved to be
useful in multiple experiments made by 3 different persons, and at
different occasions and for different purposes:
- Bug 813324 - Compiled JS cache for Firefox
- Bug 1101386 - Missing bytecode cache causes SpiderMonkey to be 6x
On Tue, Nov 24, 2015 at 02:22:44PM +0900, Mike Hommey wrote:
Note the startup cache only matters
on the first startup for a given build, and that might be a reason why
we fail to track its performance impact.
Presumably also when we flush the startup cache for changes in
add-ons?
Most
On Mon, Nov 23, 2015 at 10:26:39PM -0800, Kris Maglione wrote:
> > Most code in Firefox itself fortunately uses resource:/// instead of
> > resource://app/ (they have the same meaning, or at least were supposed
> > to, since the bug broke this promise), so it was fortunately not a
> > direct
On Tue, Nov 24, 2015 at 04:08:56PM +0900, Mike Hommey wrote:
... which seems to be a *very* old thing because:
- resource://app might have pointed to the plain Firefox directory where
you could find the omnijar a long time ago (I don't remember if that
ever was actually true), but it points
On Mon, Nov 23, 2015 at 11:29:05PM -0800, Kris Maglione wrote:
> On Tue, Nov 24, 2015 at 04:08:56PM +0900, Mike Hommey wrote:
> >... which seems to be a *very* old thing because:
> >- resource://app might have pointed to the plain Firefox directory where
> > you could find the omnijar a long time
5 matches
Mail list logo
