Implement Server Timing performance metrics

Created on 6 January 2020, over 4 years ago
Updated 30 March 2023, about 1 year ago

Problem/Motivation

Providing server timing would help developers estimate site performance.
The corresponding W3C specification is currently in "Working Draft" status and its already supported by Google Chrome and Firefox.
https://www.w3.org/TR/server-timing/
Symfony adopted it in https://github.com/symfony/symfony/pull/27985

Proposed resolution

Add Server-Timing header with relevant timing information.

Remaining tasks

Decide how enable the Server-Timing.

Proposals

  1. Add it to develoment.services.yml (#2)
  2. Enable it be default, for example by adding it to core.services.yml (#7)
  3. Create a new module for it (#24)
  4. Toggle it via service parameter (#27)
  5. Toggle it via configuration option (#38)
πŸ“Œ Task
Status

Needs work

Version

10.1 ✨

Component
Request processingΒ  β†’

Last updated 1 day ago

No maintainer
Created by

πŸ‡·πŸ‡ΊRussia Chi

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

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

  • Needs framework manager review

    It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

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.

Production build 0.69.0 2024