Open Bug 1315658 Opened 8 years ago Updated 29 days ago

Implement option to simulate CPU throttling

Categories

(DevTools :: Performance Tools (Profiler/Timeline), enhancement, P3)

enhancement

Tracking

(Not tracked)

REOPENED

People

(Reporter: sole, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [multiviewport][reserve-rdm])

Slow networks don't accurately represent low-end devices on a slow connection. We also need to slow down code execution.
No longer blocks: multiple-viewports-v1
Priority: -- → P3
Summary: Implement option to simulate CPU throttling → Implement option to simulate CPU throttling
Whiteboard: [multiviewport][reserve-rdm]
Product: Firefox → DevTools
Blocks: rdm-ux
Blocks: rdm-device
No longer blocks: rdm-ux
Type: defect → task

Don't forget that besides slow code execution, you also need slow rendering capabilities (for animated effects) and slow event dispatching.

Moving to Profiler as CPU performance is more contextual (can be exposed elsewhere, of course)

Component: Responsive Design Mode → Performance Tools (Profiler/Timeline)

Tech detail: Another product is simulating CPU throttling by regularly suspending their main thread. It should be possible to do that from our profiler sampling loop, somewhere around there: https://searchfox.org/mozilla-central/rev/5a4aaccb28665807a6fd49cf48367d47fbb5a19a/tools/profiler/core/platform.cpp#3220
(And all that code could be copied/reused elsewhere if we wanted to throttle without using the profiler.)

Type: task → enhancement
Severity: normal → S3

This report is related to the old DevTools Profiler.
The Performance panel now points to the new Firefox profiler available at profiler.firefox.com
Closing as Invalid bug

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID

I believe this is still valid.

Status: RESOLVED → REOPENED
Resolution: INVALID → ---

The new Firefox profiler doesn't provide a mechanism to simulate CPU throttling similar to Chrome DevTools.

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