• 0 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle











  • I too am skeptical.

    Mozilla cares a lot about performance. It is monitored obsessively and there are entire teams dedicated to squeezing out every last drop of performance. Heaven and earth would be moved for a 30% perf boost. I’m guessing either there’s some very severe tradeoffs to these prefs, or setting them somehow breaks the methodology used to obtain this number.

    Edit: also benchmarks can be notoriously misleading. I don’t have any opinions or knowledge on basemark (the benchmark used to get this 30% number), but speedometer v3 is the most state of the art and generally agreed upon benchmark for performance these days.

    That doesn’t mean the 30% number is bogus… Just that it should be followed by “…on basemark” rather than implying it’s conclusive to overall performance.









    1. doesnt have time, unassigns themselves

    Because someone else took over, as the person even says in a comment.

    1. Priority gets set lower

    Priority got set back to the priority it was at 4 minutes before. The priority being changed was clearly a mistake.

    1. A guy wants to work on it
    2. That guy doesnt work at Mozilla anymore

    OK?

    1. The bug went from priority P5 to P1 and doesnt block anything anymore

    It got retriaged. There are processes for this and it’s totally normal.

    This is really bad. Especially as it seems like not that big of a change.

    No it really isn’t bad at all. And it’s a massive change, the linked bug is a meta bug which means it is simply used to track the actual work. See all the bugs in the depends on section? That’s where the real work happens and there has been a ton of progress made.

    Also believe it or not, lots of discussion happens outside of bugs. You really have no idea what is going on just by looking at bug activity.