Problem/Motivation

With the items in #3591027: [META] Remove use case specific elements from Standard and Node module. Always install with Standard. Keep Minimal for CLI use only. Standard is becoming more like a starting point instead of covering a real life use case. Especially following #3572350: Disable the default /node listing view, replace Olivero hardcoded welcome page from /node with welcome message the default front page will not be a node listing. While that is moved to a dedicated disabled view and its tests are moved there, the StandardPerformanceTest remains but is now not very useful to test real life scenarios. It is a much lower level baseline now.

@berdir suggested I open an issue to move the StandardPerformanceTest to more useful tests, eg. to Umami performance testing.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

gábor hojtsy created an issue. See original summary.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Postponed

Postponing on #3572350: Disable the default /node listing view, replace Olivero hardcoded welcome page from /node with welcome message.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Title: Move/split remaining parts of StandardPerformanceTest » Move/split remaining parts of StandardPerformanceTest and StandardJavascriptTest
Status: Postponed » Active

The base issue landed. Also @berdir pointed out we also have stuff to discuss in StandardJavascriptTest, so adding this to scope to make it easier since both are standard profile performance.

catch’s picture

catch
he/him
Primary language English
commented
Related issues: +#3426303: Moving login performance testing to Umami

Looking for this I rediscovered #3426303: Moving login performance testing to Umami which was suggesting moving the login test to Umami.

catch’s picture

catch
he/him
Primary language English
commented

Put an MR up on #3426303: Moving login performance testing to Umami to move just the login testing - we should definitely keep that, and it should definitely move to the Umami test IMO.

Once that's moved, then I think we can review the rest of the test + StandardJavascriptTest here.

I think the main thing that's useful with the standard performance tests is keeping track of absolute baseline queries/cache operations/css/js that core requires to serve a page - this is why the tests already use stark instead of Olivero. But also we have NodePerformanceTest which does some of that now too.