Contrib.social

[meta] Identify necessary performance optimizations for common profiling scenarios

Open on Drupal.org →
Created on 14 April 2015, about 10 years ago
Updated 1 March 2025, about 2 months ago

Problem/Motivation

Drupal 8 has introduced many new subsystem and modules. While caching has been improved with cache tags and contexts, raw performance both of bootstrap, routing, route access checking and generating full HTML responses is significantly slower.

Proposed resolution

Profile common scenarios (standardized list being worked on at #2497185: [no patch] Create standardized core profiling scenarios and start tracking metrics for them → ) with warm, 'cool', and cold caches to identify possible optimizations.

  • Warm cache: every possible cache get is a cache hit.
  • Cool cache: site-wide caches are a hit, but cache gets specific to context are cold (i.e. the first time node/2 gets visited when other caches were warmed by /user)
  • Cold cache: most or all cache gets are a cache miss (+ router and container rebuilds).

Once issues are identified, they should be opened according to issue priority (see https://www.drupal.org/core/issue-priority → ) as a child or related issue to this one.

A performance issue is critical by itself if some of the following are true:

  • There is concrete performance issue identified by profiling (MySQL, PHP or browser equivalent) and a viable plan to resolve it
  • It can't be committed to a patch-level version (8.0.0 => 8.0.1)
  • Over ~100ms or more savings with cold caches and would have to be deferred to a minor version
  • Over ~10ms savings with warm caches and would have to be deferred to 9.x
  • Over ~1ms or more with the internal page cache and would have to be deferred to 9.x
  • Gets measurably worse with lots of contrib modules or large data sets (e.g. non-indexed queries) and would have to be deferred to a minor version
  • Other specific issues at branch maintainer discretion

Remaining tasks

  • Complete the list of 'common profiling scenarios', ensure each has been profiled and issues opened for anything found
  • Try to fix as many issues as possible before we hit zero critical issues, then repeat the profiling to see what's left and review outstanding child issues to confirm whether they're OK to fix after release or should be promoted to critical (due to necessary API changes etc.)

User interface changes

None.

API changes

N/A

🌱 Plan
Status

Closed: outdated

Version

11.0 🔥

Component

other

Created by

🇨🇦Canada webchick Vancouver 🇨🇦

Live updates comments and jobs are added and updated live.
  • Performance

    It affects performance. It is often combined with the Needs profiling tag.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment about 2 months ago →
    🇨🇭Switzerland berdir Switzerland

    This wasn't updated in almost 10 years. While some of the child issues such as the entity query one are still open, I don't think there's any gain keeping this open. We have automated performance tests, and we have issues on extending that and improving things identified there.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024