Closed Bug 1835071 Opened 1 year ago Closed 1 year ago

implement a custom start/stop for running chrome trace to profile benchmarks in CI

Categories

(Testing :: Raptor, enhancement, P1)

Default
enhancement

Tracking

(firefox120 fixed)

RESOLVED FIXED
120 Branch
Tracking Status
firefox120 --- fixed

People

(Reporter: kshampur, Assigned: kshampur)

References

(Depends on 1 open bug, Blocks 3 open bugs)

Details

(Whiteboard: [fxp])

Attachments

(1 file)

See Bug 1823730 and PR https://github.com/sitespeedio/browsertime/pull/1934

Once pageload traces are working as expected we should move forward with this

Before looking to make upstream changes, first check how the default implementation works for benchmarks

Assignee: nobody → kshampur
Status: NEW → ASSIGNED
Priority: P3 → P2

the sp3 profiles are a little useless (not surprising) e.g.

but not entirely useless like in this motionmark one

basically it cuts off too early. I will see if there any existing flags that can extend it, otherwise as suggested in https://bugzilla.mozilla.org/show_bug.cgi?id=1835071#c0, I will make an upstream change to browsertime to expose the start/stop

Priority: P2 → P1

This patch uses the custom browsertime exposed start/stop command
for using the chrome Trace. Previously the logic in browsertime
was intended for profiling pageloads, and would end prematurely before
the benchmark was completed. A similar custom start/stop approach was
done previously for the gecko profiler, and now the same thing is needed
here.

Blocks: 1848217

(In reply to Kash Shampur [:kshampur] ⌚EST from comment #5)

just fyi: pr for upstream https://github.com/sitespeedio/browsertime/pull/1988

PR has been merged

Attachment #9352998 - Attachment description: WIP: Bug 1835071 - Use custom start/stop for running chrome trace to profile benchmarks in CI. r?#perftest → Bug 1835071 - Use custom start/stop for running chrome trace to profile benchmarks in CI. r?#perftest
Blocks: 1857587
Depends on: 1857588
Attachment #9352998 - Attachment description: Bug 1835071 - Use custom start/stop for running chrome trace to profile benchmarks in CI. r?#perftest → WIP: Bug 1835071 - Use custom start/stop for running chrome trace to profile benchmarks in CI. r?#perftest
Blocks: 1858203
Attachment #9352998 - Attachment description: WIP: Bug 1835071 - Use custom start/stop for running chrome trace to profile benchmarks in CI. r?#perftest → Bug 1835071 - Use custom start/stop for running chrome trace to profile benchmarks in CI. r?#perftest
Blocks: 1858697
See Also: → 1859045
Pushed by kshampur@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0c243e4e632e Use custom start/stop for running chrome trace to profile benchmarks in CI. r=perftest-reviewers,sparky
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: