Problem/Motivation
We have node and front page anonymous performance tests for Umami, we should add authenticated tests too.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3414261
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
catchComment #4
smustgrave commentedseems to have failures
Comment #5
catchSome debug crept in, green now.
From looking at the results of this, I found #3414287: Avoid reading session from the database multiple times during a big pipe request and #3414373: Route preloading doesn't run on dynamic page cache hits for potential optimizations.
Comment #6
smustgrave commentedBased on how other performance tests are written this looks inline.
Left a small comment but not a blocker.
Comment #7
catchFound a third issue as a result of adding this and the open telemetry reports: #3414398: AssetResolver::getJsAssets() and AssetResolver::getCssAssets() can repeatedly try to calculate the same set of assets.
Comment #8
longwaveBackported to 10.2.x to keep things in sync, the performance tests are the same there so why not add this one as well.
Committed and pushed af726dbfa5 to 11.x and 45df42c385 to 10.2.x. Thanks!