Closed Bug 1812507 Opened 1 year ago Closed 1 year ago

Steady regression on AWFY-AngularJS-TodoMVC/CompletingAllItems/Sync since January 14, 2023

Categories

(Core :: Performance, defect, P3)

Product:
Core
Component:
Performance
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [sp3])

Go to https://arewefastyet.com/win10/benchmarks/raptor-desktop-speedometer?numDays=60

Look at some of the AngularJS-TodoMVC/CompletingAllItems/* benchmarks.

They appear to have a negative trend since Jan14. Difficult to say if its an actual regression, expected regression.

Moving this from Core:General to Core:Performance as a starting point. If this is wrong Component please help find the correct one.

Component: General → Performance
Blocks: speedometer3
Severity: -- → S3
Priority: -- → P3

AngularJS has been removed from the new Speedometer, I don't think we necessarily care too much about this without further context of this actually having meaningfully regressed something for our users. Please re-open if you believe this is an incorrect assessment.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX

Are there plans to update AWFY to the new Speedometer3 benchmark, or a bug i can follow?
I dont want to file regression bugs that are not relevant/obsolete.

Flags: needinfo?(bas)
Whiteboard: [sp3]

(In reply to Mayank Bansal from comment #3)

Are there plans to update AWFY to the new Speedometer3 benchmark, or a bug i can follow?
I dont want to file regression bugs that are not relevant/obsolete.

Not that I know of right now. But you can find the status of all the current Speedometer 3 benchmarks through our dashboard here: https://mozilla-hub.atlassian.net/wiki/spaces/FIREFOX/pages/189595770/Speedometer+3+Dashboard the individual platform overviews will also link to the relevant perfherder graphs.

Flags: needinfo?(bas)

I dont have access to this confluence. "<my bugzilla email id> doesn't have access to Confluence on mozilla-hub.atlassian.net."

Yeah, that is link is very much internal. We should have something public, I think.

There is public data for this in https://treeherder.mozilla.org/perfherder/graphs, but it's not included in AWFY atm. Generally speaking though - we have tools for tracking changes to these tests and linking them back to bugs, and so I don't think people need to track them manually. Though if you've discovered a regression here that was missed by tools that would be good to know as that may highlight something to fix. Maybe it's the case that we don't currently alert on individual step improvement / regressions (only the total time)?

You need to log in before you can comment on or make changes to this bug.