Performance team meeting summary 21 June 2022

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Site Health

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
  • @shetheliving: Added new autoloaded options section to the Optimization doc and will create a PR to link to it in the autoloaded options Site Health report when ready. Also attended documentation trainings last week and now have edit access for docs, so feel free to loop me in if you need help there.
  • @mukesh27: PR #380 is ready to merge; @spacedmonkey merged

Feedback requested

Measurement

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
  • @flixos90: Working on a blog post for Make about the plugin checker proposal; should be ready to post early next week

Feedback requested

JavaScript

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Infrastructure

@flixos90

GitHub project

Feedback requested

6.1 release plans

  • @furi3r: Are we thinking of porting some of the modules to core for 6.1, specifically Site Health?
    • @furi3r: Full page cache is not experimental, but fairly new. Autoloaded Options could be a good candidate if we can get the documentation updated.
    • @spacedmonkey: Would love to see Autoloaded Options in 6.1
    • @flixos90: We can get Object Cache and Full Page Cache in 6.1 if we move them forward, but the other two are more of a stretch. Reminder to review the lifecycle of a performance module doc if you haven’t already.
    • @spacedmonkey: Should we create Trac tickets for each of the Site Health modules?
      • @flixos90: That would be good, but main thing is feature proposals
      • @spacedmonkey: Do these even need feature proposals, as additions to an existing feature?
      • @flixos90: Depends on how you frame it. I think they’re large enough to justify feature proposals. Mostly critical to get more feedback around the heuristics being used to determine if a check is “passed” or not.
      • @spacedmonkey: Since they’re small, maybe multiple in one post?
      • @flixos90: For related ones, maybe. Some are larger, e.g. Object Cache and Full Page Cache, and should be their own posts.
      • @spacedmonkey: What about the WebP check? Is that part of the WebP core merge?
      • @flixos90: It’s a bit decoupled, but should go in with the WebP feature if not sooner.
    • @flixos90: Who here can work on getting some of the other Site Health modules and/or dominant color merged into core?
    • @shetheliving: Tentatively aim to include Autoloaded Options check in 6.2 pending docs

Open floor

Help wanted

#core-js, #core-media, #performance, #performance-chat, #summary

#hosting-community, #tide

Leave a Reply

Your email address will not be published. Required fields are marked *