It's ok to mention Chirp publicly.  (Chirp is just a tool that sends automated alerts when metrics change significantly.)  Thanks for filing this follow-up bug!

I've just opened a local tab and will look every now and then. Chirp notifications would not be useful IMO.

Speaking of which... the metrics as of today do highlight poor scheduler configuration with the increased workload (last time we looked at this was over a year ago). Now many threads detach after running only 1 task and many threads go back to sleep without running a single task when woken up.

Will repuprose this bug to track that.

FTR, here's a dashboard with the majority of our metrics https://uma.googleplex.com/histograms?endDate=latest&dayCount=1&histograms=TaskScheduler.DetachDuration.Browser.BackgroundBlockingPool%2CTaskScheduler.DetachDuration.Browser.BackgroundPool%2CTaskScheduler.DetachDuration.Browser.ForegroundBlockingPool%2CTaskScheduler.DetachDuration.Browser.ForegroundPool%2CTaskScheduler.DetachDuration.Renderer.BackgroundBlockingPool%2CTaskScheduler.DetachDuration.Renderer.BackgroundPool%2CTaskScheduler.DetachDuration.Renderer.ForegroundBlockingPool%2CTaskScheduler.DetachDuration.Renderer.ForegroundPool%2CTaskScheduler.NumTasksBeforeDetach.Browser.BackgroundBlockingPool%2CTaskScheduler.NumTasksBeforeDetach.Browser.BackgroundPool%2CTaskScheduler.NumTasksBeforeDetach.Browser.ForegroundBlockingPool%2CTaskScheduler.NumTasksBeforeDetach.Browser.ForegroundPool%2CTaskScheduler.NumTasksBeforeDetach.Renderer.BackgroundBlockingPool%2CTaskScheduler.NumTasksBeforeDetach.Renderer.BackgroundPool%2CTaskScheduler.NumTasksBeforeDetach.Renderer.ForegroundBlockingPool%2CTaskScheduler.NumTasksBeforeDetach.Renderer.ForegroundPool%2CTaskScheduler.NumTasksBetweenWaits.Browser.BackgroundBlockingPool%2CTaskScheduler.NumTasksBetweenWaits.Browser.BackgroundPool%2CTaskScheduler.NumTasksBetweenWaits.Browser.ForegroundBlockingPool%2CTaskScheduler.NumTasksBetweenWaits.Browser.ForegroundPool%2CTaskScheduler.NumTasksBetweenWaits.Renderer.BackgroundBlockingPool%2CTaskScheduler.NumTasksBetweenWaits.Renderer.BackgroundPool%2CTaskScheduler.NumTasksBetweenWaits.Renderer.ForegroundBlockingPool%2CTaskScheduler.NumTasksBetweenWaits.Renderer.ForegroundPool%2CTaskScheduler.TaskLatencyMicroseconds.Browser.BackgroundTaskPriority%2CTaskScheduler.TaskLatencyMicroseconds.Browser.BackgroundTaskPriority_MayBlock%2CTaskScheduler.TaskLatencyMicroseconds.Browser.UserBlockingTaskPriority%2CTaskScheduler.TaskLatencyMicroseconds.Browser.UserBlockingTaskPriority_MayBlock%2CTaskScheduler.TaskLatencyMicroseconds.Browser.UserVisibleTaskPriority%2CTaskScheduler.TaskLatencyMicroseconds.Browser.UserVisibleTaskPriority_MayBlock%2CTaskScheduler.TaskLatencyMicroseconds.Renderer.BackgroundTaskPriority%2CTaskScheduler.TaskLatencyMicroseconds.Renderer.BackgroundTaskPriority_MayBlock%2CTaskScheduler.TaskLatencyMicroseconds.Renderer.UserBlockingTaskPriority%2CTaskScheduler.TaskLatencyMicroseconds.Renderer.UserBlockingTaskPriority_MayBlock%2CTaskScheduler.TaskLatencyMicroseconds.Renderer.UserVisibleTaskPriority%2CTaskScheduler.TaskLatencyMicroseconds.Renderer.UserVisibleTaskPriority_MayBlock&fixupData=true&showMax=true&filters=platform%2Ceq%2CW%2Cchannel%2Ceq%2C4%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial#TaskScheduler.TaskLatencyMicroseconds.Browser.UserBlockingTaskPriority_MayBlock

etiennep@ is looking at the scheduler configs already and tracking elsewhere, archiving this one