Open Bug 1755559 Opened 4 years ago Updated 3 years ago

--gecko-profile does not work for displaylist_mutate talos test

Categories

(Testing :: Performance, defect, P2)

defect

Tracking

(firefox-esr91 unaffected, firefox97 wontfix, firefox98 wontfix, firefox99 wontfix, firefox100 affected)

Tracking Status
firefox-esr91 --- unaffected
firefox97 --- wontfix
firefox98 --- wontfix
firefox99 --- wontfix
firefox100 --- affected

People

(Reporter: mikokm, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: leave-open, regression)

Attachments

(1 file)

STR: |mach talos-test -a displaylist_mutate --gecko-profile|

20:36:37     INFO -   'TPPROFILINGINFO': '{"gecko_profile_interval": 2, "gecko_profile_entries": '
20:36:37     INFO -                      '2000000, "gecko_profile_dir": "/tmp/tmptxc1p3ka", '
20:36:37     INFO -                      '"gecko_profile_features": '
20:36:37     INFO -                      '"js,leaf,stackwalk,cpu,threads", "gecko_profile_threads": '
20:36:37     INFO -                      '"GeckoMain,Compositor,WR,Renderer"}',

The profiler warns

Unrecognized feature "threads".

and the profiles seem to contain only few seconds of measurements.

Looks like we have two remaining holdovers of the threads feature: https://searchfox.org/mozilla-central/search?q=cpu%2Cthreads&path=

Keywords: regression
Regressed by: 1729815

Set release status flags based on info from the regressing bug 1729815

I removed the threads parameter locally and encountered another issue. The profiles seem to only record some portions of the test end.
Increasing the value here https://searchfox.org/mozilla-central/source/testing/talos/talos/test.py#1137 seems to fix it.

Thank you for looking into this.

The "threads" feature hasn't done anything for a long time, so other issues would be unrelated.
Yes, increasing the number of "entries" should help with too-short profiles.

I'd be happy to review if you'd like to submit a patch. Please let me know otherwise.

Severity: -- → S4
Priority: -- → P3
Has Regression Range: --- → yes
Severity: S4 → --
Component: Gecko Profiler → Performance
Priority: P3 → --
Product: Core → Testing
Assignee: nobody → florian
Status: NEW → ASSIGNED
Blocks: dev-pain
Severity: -- → S3
Priority: -- → P2
Priority: P2 → P1
Pushed by fqueze@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a742bb7e5a16 remove the obsolete 'threads' profiler feature from automated performance tests, r=mstange,perftest-reviewers,sparky.

Unassigning, as I think Greg wanted to keep this bug open to fix the profiler buffer size (ideally the buffer size used for all perf tests should be reviewed and made large enough for this to not be a problem again for another test).

Assignee: florian → nobody
Status: ASSIGNED → NEW
Priority: P1 → P2

Hey Sparky,
Do we want to keep this open?
Also, is there a bug ticket opened for any further work?
Thanks.

Flags: needinfo?(gmierz2)

Yes, we should leave this open until the issue Florian mentioned (buffer size) is resolved.

Flags: needinfo?(gmierz2)

The leave-open keyword is there and there is no activity for 6 months.
:andrej, maybe it's time to close this bug?
For more information, please visit auto_nag documentation.

Flags: needinfo?(aglavic)
Flags: needinfo?(aglavic)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: