📍 Job mac-m1_mini_2020-perf/blink_perf.bindings complete.
See results at: https://pinpoint-dot-chromeperf.appspot.com/job/17bdb32e490000
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
📍 Job mac-m1_mini_2020-perf/blink_perf.css complete.
See results at: https://pinpoint-dot-chromeperf.appspot.com/job/120f5582490000
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
📍 Job mac-m1_mini_2020-perf/blink_perf.layout complete.
See results at: https://pinpoint-dot-chromeperf.appspot.com/job/10fb3ea6490000
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
📍 Job mac-m1_mini_2020-perf/blink_perf.dom complete.
See results at: https://pinpoint-dot-chromeperf.appspot.com/job/12b5b16a490000
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
# Exposition on patchset 7
For now, I think I'd like to get this set landed so I can continue iterating without carrying around this large delta.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Over to Daniel as a Gerrit-suggested reviewer (and apparently indirect owner of just about every file here).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
I guess I'm OK with this but I have some overall concerns:
1. Let's try to link some non-Google-internal docs from the CL description for additional context for readers. Let's try to address this before landing; I don't think most of this context needs to be internal only.
2. More generally, where `base::unchecked` gets sprinkled in looks quite arbitrary, and it's easy to get copied and pasted to places it doesn't need (and it seems like it's also easy to introduce small performance regressions/hotspots if we're not careful). That doesn't seem great and it seems like something we'll need to think about for long-term maintainability... I think it's one thing if we just needed it in a few spots; it's another thing to have it spread out over 30+ files (so far, and presumably potentially more in the future).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I guess I'm OK with this but I have some overall concerns:
1. Let's try to link some non-Google-internal docs from the CL description for additional context for readers. Let's try to address this before landing; I don't think most of this context needs to be internal only.
2. More generally, where `base::unchecked` gets sprinkled in looks quite arbitrary, and it's easy to get copied and pasted to places it doesn't need (and it seems like it's also easy to introduce small performance regressions/hotspots if we're not careful). That doesn't seem great and it seems like something we'll need to think about for long-term maintainability... I think it's one thing if we just needed it in a few spots; it's another thing to have it spread out over 30+ files (so far, and presumably potentially more in the future).
1. Done --- pasted the original design doc into the public explainer. Please let me know if you want anything else.
1. nuskos@ suggested we could (as a precondition to launch) just whack a check for this into the presubmit in the vein of `RAW_PTR_EXCLUSION` and friends. Hopefully that would mostly mitigate.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
9 is the latest approved patch-set.
No files were changed between the latest approved patch-set and the submitted one.
Checked Span: Address `blink_perf` suites
This change doesn't introduce any behavioral change. The context for
this CL is given by:
https://docs.google.com/document/d/1kduT2_nbBMd49_J2K2Jvw9Z6M18itKz6AIS1S7HMocg/edit?tab=t.0
The linked doc also attaches a public version of the original design
doc.
Looking at the alerts that fired when we last tried to enable Checked
Span in release, `blink_perf` suites are strongly affected.
This CL opts out spans in several places, particularly `renderer/core/`.
It's guided by what pprof surfaces when individual `blink_perf` suites
are run.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |