That's correct. It means that benchmarking on nighties isn't really
accurate so beware when running web/js benchmarks. Also it is wrong to
assume an average performance cost and scale the nightly results by a
factor.
We made this decision with the hope that we could better gather performance
data
On 2013-11-09 6:30 PM, Boris Zbarsky wrote:
On 11/9/13 12:53 PM, Philip Chee wrote:
Not directly related but. Some time back I wanted to turn on profiling
for SeaMonkey on our trunk builds but was vetoed because turning on
profiling (I was told) causes a pref hit.
It does, but a pretty small o
On 11/9/13 12:53 PM, Philip Chee wrote:
Not directly related but. Some time back I wanted to turn on profiling
for SeaMonkey on our trunk builds but was vetoed because turning on
profiling (I was told) causes a pref hit.
It does, but a pretty small one, and only on x86-32 (because there is
one
On 09/11/2013 02:38, Ehsan Akhgari wrote:
> Hi everyone,
>
> I set up the profiling branch a long time ago to build mozilla-central
> without the --enable-profiling option to catch any regressions that happen
> in those builds to minimize the chance of things blowing up after an uplift
> to Aurora
Hi everyone,
I set up the profiling branch a long time ago to build mozilla-central
without the --enable-profiling option to catch any regressions that happen
in those builds to minimize the chance of things blowing up after an uplift
to Aurora (which is always built without --enable-profiling.)
5 matches
Mail list logo