On Tue, Sep 25, 2012 at 7:17 PM, Daniel Buchner wrote:
> I will talk with Alex about all of the concerns you've raised (hopefully
> this week)
>
> Hopefully we can get everything straightened out and produce another great
> benchmark option that we can all consume/contribute to!
https://github.co
I've got private access to the RoboHornet repo and have been in discussions
with the PM that headed that effort up, do you all want to get some code
committed to help our numbers out?
- Daniel
On Tue, Sep 25, 2012 at 6:51 AM, Justin Lebar wrote:
> > (Can you hear that thud, thud, thud? It's the
I will talk with Alex about all of the concerns you've raised (hopefully
this week)
Hopefully we can get everything straightened out and produce another great
benchmark option that we can all consume/contribute to!
- Daniel
On Sep 25, 2012 7:03 PM, "Nicholas Nethercote"
wrote:
> On Tue, Sep 25,
This was not pitched to me by the folks involved as being our official
buy-in for this test. They asked me to try and get our people involved and
help. I helped get some of the tests working that were crashing in Fx. I
thought I was doing something good to help us not get docked for crashing
tests.
I know the principal Google PM, Alex K, who heads up RoboHornet - he has
been extremely helpful with our Web Components initiative. I believe he had
good intentions with RoboHornet, and his personal posts (and those of Paul
Irish) did not claim Google had Mozilla's official organizational support
f
On Tue, Sep 25, 2012 at 6:23 PM, Daniel Buchner wrote:
> I know the principal Google PM, Alex K, who heads up RoboHornet - he has
> been extremely helpful with our Web Components initiative. I believe he had
> good intentions with RoboHornet, and his personal posts (and those of Paul
> Irish) did
On Wed, Sep 26, 2012 at 9:37 AM, Kevin Gadd wrote:
> Has anyone reached out directly to the guys running the benchmark to
> try and get a feel for what their motivations are here? They may
> actually be willing to do the work necessary to make this a good
> benchmark.
Justin filed https://github.
Has anyone reached out directly to the guys running the benchmark to
try and get a feel for what their motivations are here? They may
actually be willing to do the work necessary to make this a good
benchmark.
I spent an hour or two going over some of their tests and making
suggestions on their gi
On Tue, Sep 25, 2012 at 6:51 AM, Justin Lebar wrote:
>
> One of the intriguing things about this benchmark is that it's open
> source, and they're committed to changing it over time.
>
> FWIW Paul Irish agrees the sieve is a bad test, although he doesn't
> hate it to the extent you or i would thin
On 26/09/12 04:25, daniel...@gmail.com wrote:
Yeah, press apparently didn't distinguish between the two - and I never asked,
or was placed on the Technical Adviser list.
No good deed goes unpunished.
On the bright side, I never saw Firefox lagging hardcore in my testing - in
fact, as this
Yeah, press apparently didn't distinguish between the two - and I never asked,
or was placed on the Technical Adviser list.
On the bright side, I never saw Firefox lagging hardcore in my testing - in
fact, as this article corroborates, we can do pretty darn good on most tests,
and even took the
On 9/25/12 11:54 AM, dang...@gmail.com wrote:
I think it's interesting that most of the people on the RoboHornet committee
are web developers and not browser developers.
That's purposeful. See
https://github.com/robohornet/robohornet/wiki/Committee-Charter and
compare to https://github.com/
On Tuesday, September 25, 2012 11:34:14 AM UTC-4, Justin Lebar wrote:
> > Regardless, my name is off the list, and I never knew it would be used that
> > way.
>
> I did not mean to imply that somehow your being involved was wrong or
> could be used against us. We ought to be able to participate
Yeah, some were crashing that I tested (mostly canvas), but were fixed. Again,
I never intended this.
***dbuc returns to woodshed :(
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
> Regardless, my name is off the list, and I never knew it would be used that
> way.
I did not mean to imply that somehow your being involved was wrong or
could be used against us. We ought to be able to participate in
interesting projects without "endorsing" them. I for one think it's
great th
I didn't mean "win", in fact I never said that. I simply meant if a test was
not written well or using an API improperly/poorly that we could correct things
like that. I certainly didn't mean we should game anything.
Regardless, my name is off the list, and I never knew it would be used that way
On 9/25/12 10:56 AM, Justin Lebar wrote:
Maybe this is naive of me, but I for one don't really believe in
tweaking benchmarks for the purposes of making Firefox look better.
Indeed. The goal here is to have a good benchmark, not one that we "win".
Anyway, I filed a bug on getting rid of the
This was not pitched to me by the folks involved as being our official buy-in
for this test. They asked me to try and get our people involved and help. I
helped get some of the tests working that were crashing in Fx. I thought I was
doing something good to help us not get docked for crashing tes
Maybe this is naive of me, but I for one don't really believe in
tweaking benchmarks for the purposes of making Firefox look better.
If we look bad in a benchmark, badmouthing it seems somehow more
gentlemanly than stacking it. :)
Anyway, I filed a bug on getting rid of the microbenchmarks, whic
> (Can you hear that thud, thud, thud? It's the sound of me beating my head
> against my desk.)
One of the intriguing things about this benchmark is that it's open
source, and they're committed to changing it over time.
FWIW Paul Irish agrees the sieve is a bad test, although he doesn't
hate it t
On Tuesday, 25 September 2012 17:42:00 UTC+12, Nicholas Nethercote wrote:
> On Mon, Sep 24, 2012 at 5:22 PM, wrote:
>
> > So there's a new benchmark out, seemingly from google.
>
> >
>
> > It is designed to test performance in web app bottlenecks, especially "DOM,
> > API methods, SVG".
>
>
On Mon, Sep 24, 2012 at 5:22 PM, Tim wrote:
> So there's a new benchmark out, seemingly from google.
>
> It is designed to test performance in web app bottlenecks, especially "DOM,
> API methods, SVG".
>
> Paul Irish from Google's Chrome team is in charge of it. He blogged on it
> here:
>
> htt
Oops, here's the benchmark site:
http://www.robohornet.org/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
So there's a new benchmark out, seemingly from google.
It is designed to test performance in web app bottlenecks, especially "DOM,
API methods, SVG".
Paul Irish from Google's Chrome team is in charge of it. He blogged on it here:
http://paulirish.com/2012/a-browser-benchmark-that-has-your-back
24 matches
Mail list logo
