docs: devtools throttling deprecation notice #9933

connorjclark · 2019-11-06T19:26:49Z

This doc will added via a link next to the throttling option in DevTools.

CL: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1885347

brendankenny · 2019-11-06T19:54:33Z

Would this be better on devsite or in a "What's New In DevTools" post? Seems weird to document here for whatever reason (but also fine :)

paulirish · 2019-11-06T20:03:15Z

nah it's great here. just perfect. really the finest location. best place on earth.

paulirish · 2019-11-06T20:03:33Z

but i'm actually gonna merge this lil thing into the throttling.md doc and it'll be even better then.

paulirish · 2019-11-06T20:23:51Z

https://github.com/GoogleChrome/lighthouse/blob/dt-deprecation/docs/throttling.md#audits-panel-throttling-settings

patrickhulce

solid plan 👍

patrickhulce · 2019-11-06T20:39:25Z

docs/throttling.md

-1. **_Request-level_** throttling, also referred to as _DevTools throttling_ or in the Audits Panel as _Applied throttling_, is how throttling is implemented with Chrome DevTools. In real mobile connectivity, latency affects things at the packet level rather than the request level. As a result, this throttling isn't highly accurate. It also has a few more downsides that are summarized in [Network Throttling & Chrome - status](https://docs.google.com/document/d/1TwWLaLAfnBfbk5_ZzpGXegPapCIfyzT4MWuZgspKUAQ/edit). The TLDR: while it's a [decent approximation](https://docs.google.com/document/d/10lfVdS1iDWCRKQXPfbxEn4Or99D64mvNlugP1AQuFlE/edit), it's not a sufficient model of a slow connection. The [multipliers used in Lighthouse](https://github.com/GoogleChrome/lighthouse/blob/3be483287a530fb560c843b7299ef9cfe91ce1cc/lighthouse-core/lib/emulation.js#L33-L39) attempt to correct for the differences.
-1. **_Proxy-level_** throttling tools do not affect UDP data, so they're decent, but not ideal.
+1. **_Request-level throttling_** , also referred to as **_Applied throttling_** in the Audits panel or _`devtools` throttling_ in Lighthouse configuration, is how throttling is implemented with Chrome DevTools. In real mobile connectivity, latency affects things at the packet level rather than the request level. As a result, this throttling isn't highly accurate. It also has a few more downsides that are summarized in [Network Throttling & Chrome - status](https://docs.google.com/document/d/1TwWLaLAfnBfbk5_ZzpGXegPapCIfyzT4MWuZgspKUAQ/edit). The TLDR: while it's a [decent approximation](https://docs.google.com/document/d/10lfVdS1iDWCRKQXPfbxEn4Or99D64mvNlugP1AQuFlE/edit), it's not a sufficient model of a slow connection. The [multipliers used in Lighthouse](https://github.com/GoogleChrome/lighthouse/blob/3be483287a530fb560c843b7299ef9cfe91ce1cc/lighthouse-core/lib/emulation.js#L33-L39) attempt to correct for the differences.
+1. **_Proxy-level_** tools do not affect UDP data, so they're decent, but not ideal.


feels weird to remove it just from here, Proxy-level tools but Packet-level throttling tools

what motivated the removal?

patrickhulce · 2019-11-06T20:39:59Z

docs/throttling.md

+
+Starting with Chrome 80, the Audits panel is simplifying the throttling configuration. To wit:
+
+1. _Simulated throttling_ becomes the default setting. This matches the setup of PageSpeed Insights and the Lighthouse CLI default, so you should see more consistent results.


wasn't it already the default for new users? are we just removing the stickiness?

okay yah. reworded.

I think calling out that it will become the only option is what's important.

ChromeCAB

I like it. :)

egsweeny

This looks great. :)

brendankenny · 2019-11-06T20:24:40Z

docs/throttling.md

+
+In Chrome 79 and earlier, you could choose between [the throttling types](#types-of-throttling) of Simulated, Applied, and none.
+
+Starting with Chrome 80, the Audits panel is simplifying the throttling configuration. To wit:


Suggested change

Starting with Chrome 80, the Audits panel is simplifying the throttling configuration. To wit:

Starting with Chrome 80, the Audits panel is simplifying the throttling configuration.

brendankenny · 2019-11-06T20:25:27Z

docs/throttling.md

+
+1. _Simulated throttling_ becomes the default setting. This matches the setup of PageSpeed Insights and the Lighthouse CLI default, so you should see more consistent results.
+1. _No throttling_ is removed as it leads to innacurate scoring and misleading metric results.
+1. Within the Audits panel settings, you can uncheck the _Simulated throttling_ checkbox to use _Applied throttling_.


fwiw a radio button seems significantly less confusing for this. If "Simulated Throttling" is unchecked I would assume it's not throttled, personally

it's super weird. i agree. so let's get a reasonable lantern trace generated and then we can drop this silliness.

it's super weird. i agree. so let's get a reasonable lantern trace generated and then we can drop this silliness.
-- former UX engineer Paul Irish

:P

brendankenny · 2019-11-06T20:26:38Z

docs/throttling.md

-Lighthouse, by default, uses simulated throttling as it provides both quick evaluation and minimized variance. However, some may want to experiment with more accurate throttling...
+Lighthouse, by default, uses simulated throttling as it provides both quick evaluation and minimized variance. However, some may want to experiment with more accurate throttling... [Learn more about these throttling types and how they behave in in different scenarios](https://www.debugbear.com/blog/network-throttling-methods).
+
+## Audits Panel Throttling Settings


maybe call out DevTools Audits Panel clearly here

brendankenny · 2019-11-06T20:56:29Z

docs/throttling.md

+
+For the moment, we are keeping _Applied throttling_ option available for users of the [`View Trace` button](https://developers.google.com/web/updates/2018/04/devtools#traces). Under applied throttling, the trace matches the metrics values, whereas under Simulated things do not currently match up.
+
+We plan to improve the experience of viewing a trace under simulated throttling. At that point, the _Applied throttling_ option will be removed from the Audits panel. Of course, CLI users can still control the exact [configuration](../#cli-options) of throttling.


I guess somehow DevTools isn't for power users anymore :P

docs: devtools throttling deprecation notice

faf45b6

connorjclark requested a review from paulirish as a code owner November 6, 2019 19:26

googlebot added the cla: yes label Nov 6, 2019

paulirish added 2 commits November 6, 2019 12:21

merge deprecation notice into throttling md, untouched

ba811bb

rewrite dt throttling notice a bit

1125449

vercel bot deployed to staging November 6, 2019 20:23 View deployment

patrickhulce approved these changes Nov 6, 2019

View reviewed changes

ChromeCAB approved these changes Nov 6, 2019

View reviewed changes

egsweeny approved these changes Nov 6, 2019

View reviewed changes

brendankenny reviewed Nov 6, 2019

View reviewed changes

hulce feedback

e39b946

vercel bot deployed to staging November 6, 2019 20:57 View deployment

kenny feedback

65808a3

vercel bot deployed to staging November 6, 2019 21:01 View deployment

the ONLY option. clark feedback

6d0d165

vercel bot deployed to staging November 6, 2019 21:11 View deployment

paulirish merged commit 3acba79 into master Nov 7, 2019

paulirish deleted the dt-deprecation branch November 7, 2019 01:02

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs: devtools throttling deprecation notice #9933

docs: devtools throttling deprecation notice #9933

connorjclark commented Nov 6, 2019

brendankenny commented Nov 6, 2019 •

edited

Loading

paulirish commented Nov 6, 2019

paulirish commented Nov 6, 2019

paulirish commented Nov 6, 2019

patrickhulce left a comment

patrickhulce Nov 6, 2019

paulirish Nov 6, 2019

patrickhulce Nov 6, 2019

paulirish Nov 6, 2019

connorjclark Nov 6, 2019

ChromeCAB left a comment

egsweeny left a comment

brendankenny Nov 6, 2019

brendankenny Nov 6, 2019

paulirish Nov 6, 2019

brendankenny Nov 6, 2019

brendankenny Nov 6, 2019

brendankenny Nov 6, 2019


		Starting with Chrome 80, the Audits panel is simplifying the throttling configuration. To wit:

		1. _Simulated throttling_ becomes the default setting. This matches the setup of PageSpeed Insights and the Lighthouse CLI default, so you should see more consistent results.


		In Chrome 79 and earlier, you could choose between [the throttling types](#types-of-throttling) of Simulated, Applied, and none.

		Starting with Chrome 80, the Audits panel is simplifying the throttling configuration. To wit:


		For the moment, we are keeping _Applied throttling_ option available for users of the [`View Trace` button](https://developers.google.com/web/updates/2018/04/devtools#traces). Under applied throttling, the trace matches the metrics values, whereas under Simulated things do not currently match up.

		We plan to improve the experience of viewing a trace under simulated throttling. At that point, the _Applied throttling_ option will be removed from the Audits panel. Of course, CLI users can still control the exact [configuration](../#cli-options) of throttling.

docs: devtools throttling deprecation notice #9933

docs: devtools throttling deprecation notice #9933

Conversation

connorjclark commented Nov 6, 2019

brendankenny commented Nov 6, 2019 • edited Loading

paulirish commented Nov 6, 2019

paulirish commented Nov 6, 2019

paulirish commented Nov 6, 2019

patrickhulce left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ChromeCAB left a comment

Choose a reason for hiding this comment

egsweeny left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

brendankenny commented Nov 6, 2019 •

edited

Loading