Bethany Chobanian Lang 5:38 pm on November 29, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance Chat Summary: 29 November 2022

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

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

@mukesh27: Working on Regenerate thumbnail duplication webp file #575
@mxbclang: Noting a few items that are able to picked up if anyone has interest/capacity; see Needs Dev below
@adamsilverstein: fetchpriority experimental module was merged last week and is planned for release in v1.8.0 in December

Feedback requested

See above
Needs Discussion (10 issues)
Needs Dev (2 issues)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Focusing on theme.json parsing issues, so lots of code review. Working on:

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Measurement

N/A

GitHub project

No updates

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (4 issues)
Needs Review (2 issues)

Database

@olliejones

GitHub project

@mxbclang: What are the next steps on Revisit indexes for DB performance #132?
- @olliejones: Current voting winner points to doing something dbms-version-specific to the schema, eventually in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., think we can do this in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party if we’re willing to accept a mu-plugin drop-in module. Disadvantage here is complexity.
- @flixos90: This is tricky – we have a voting winner, but also some strong opinions from different sides including a WP lead developer.
- @mxbclang: Seems like the best next step here would be to close out the vote as planned but hold on next steps pending further discussion in the issue, then regroup on this in a future chat
- All agreed; vote will close and @mxbclang will add a comment about next steps
@olliejones: SQLite Object Cache is coming along nicely; will create a new module proposal issue once it’s closer to complete
@olliejones: For future discussion: Do we need some sort of formal set of filters, etc. to support the big competent hosting providers in this back-end area?

Feedback requested

Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Been working on iterating on the Server-Timing API PR. Still in draft because unit tests need to be added, but ready for review. Would love feedback and opinions on the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. implementation. The most important recent change is that it is now initialized early through a drop-in, so it can capture measurements that happen before WP plugins are loaded.

Feedback requested

See above
Needs Discussion (5 issues)
Needs Review (3 issues)

Open floor

@olliejones: There’s a sustainability team forming – see #sustainability Slack channel
@nickchomey: Been working on implementing a real PWA for a site under development. Plugin options are limited right now but @westonruter‘s plugin is the right approach. Is this something that the performance team can move forward?
- @flixos90: Not sure what the current state of the plugin is; original idea was for it to be a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.
- @nickchomey: Proposing a real coordinated effort be made to improve it to the point that it could be merged into core
- @flixos90: It could definitely be feature plugin material, but as always it requires resources. If a small group is up for tackling, we would be supportive and help here possible.
- @westonruter: The plugin is stable and essentially in maintenance mode. Not clear if there is the 80% user benefit to justify core merge just yet. See discussion between @nickchomey and @westonruter in GH issue: https://github.com/GoogleChromeLabs/pwa-wp/issues/884.
- @flixos90: Key aspect of proposing this for core would be to come with an actual usage of PWA capabilities that immediately benefits core users
- @westonruter: Benefit that all users could get now is offline browsing on the front-end, but there’s a separate concern of what happens when a large portion of the web is registering service workers
- @pbearne: Aren’t we going to need something like this for real-time multi-editing in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/?
- @olliejones: Maybe the Twenty Twenty Four theme could be made PWA-friendly?

Our next chat will be held on Tuesday, December 6, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

#meta

Emily Clarke 5:02 pm on November 22, 2022
Tags: core-js, core-media ( 94 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance Chat Summary: 22 November 2022

The full chat log is available beginning here on Slack.

Announcements

@clarkeemily thanked the team for the 1.7.0 release yesterday

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

No updates

Feedback requested

See above
Needs Discussion (10 issues)
Needs Review (1 issue)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey working on several TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets (Don’t use _prime_post_caches() if meta/terms cache should be updated and Implement wp_cache_get_multiple() in wp_queue_posts_for_term_meta_lazyload())
@spacedmonkey also worked on theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. parsing including:

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Measurement

N/A

GitHub project

No updates

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Needs Discussion (4 issues)
Needs Review (2 issues)

Database

@olliejones

GitHub project

@aristath continues to refine the SQLite module, and it’s pending a review so we can merge it
@aristath started working on a draft post to publish on make when the SQLite module gets merged, to invite testers.
@aristath having difficulty running performance A/B tests for the WP-CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. classes autoloader POC. This one is going to take some more time.
@OllieJones has been working on an sqlite-object-cache pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (see repo). He mentioned it in last week’s meeting, but the question is whether we want to include this as a module in the performance-lab plugin. Right now it’s standalone and works perfectly fine. My personal opinion is it should be considered as a module… SQLite is universal and can therefore be used in Core to improve performance as a caching mechanism.

Feedback requested

Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

No updates

Feedback requested

See above
Needs Discussion (5 issues)
Needs Review (3 issues)

Open floor

@oandregal asked: for folks working around wp_get_theme etc. Wanted to share a cross-PRs comment. I’m having troubles following direction regarding whether or not to use wp_get_theme. This PR proposes removing it from some places (backports changes from core), while these other two proposes to add it to a few hotpaths. Would you mind clarifying direction and nuances in this thread? Thank you.
- @spacedmonkey has replied on the PR
- @flixos90 also advised his response would be the same, we want to avoid calling wp_get_theme() multiple times where it can be called once instead. It’s not that we shouldn’t use the function anymore, just be conscious of limiting its usage to when it’s necessary
  - @10upsimon Perhaps a discussion for elsewhere @flixos90 but has there been consideration for a singleton instance response? i.e wp_get_theme() returns a singleton instance ( ::get_instance()) as opposed to instantiating a new class with each function return statement? Is there ever a valid cause for re-instantiating the WP_Theme class? I’m sure it’s far more complex and involved than I make it out to be, and I’d assume that this has been considered.
  - @spacedmonkey and @flixos90 advised we shouldn’t use singleton. But even if we use a global, there is a potential risk: Object instances are mutable so if any change was made on one instance returned from the function, it would affect every other instance if we went with a scenario where no new entity was returned on every call. For the most part this could be a backward compatibility break. So I’m not really sure this would be a worthwhile effort
@clarkeemily Just to call out there are currently 15 open issues marked as ‘Needs Review‘ across all focus areas and please keep an eye out for any PRs that may need review alongside these
- @cpal I’ve recently been looking for ways we can leverage our in-house performance/load/functional testing solution at Pressidium® to help out the core-performance team in whatever way we can but I haven’t found something totally relevant just yet. I’m happy to share details on what we currently have available in the testing realm and what is yet to come.
  After having a brief into chat with @aristath, I believe we may be able to get something going with some of the work he is currently tackling after some further discussion.
  What do you all think?? Help a noob out that’s eagerly looking to find his footing in the WP Community by throwing out some relevant suggestions if-ever/whenever you can!
  - @adamsilverstein asked if a brief overview could be provided on testing in the context of WordPress Performance
  - Pressidium is a managed/HA hosting provider and I’m tasked with performance testing that we currently use to test out client sites and services depending on the needs on the client but since we went through (and are continuing with) developing a testing infrastructure we want to give back to the WP community with it all.
  - Further discussion / introduction ongoing here in the SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. chat

Our next chat will be held on Tuesday, November 29, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

Felix Arntz 8:16 pm on November 15, 2022
Tags: core-js, core-media ( 94 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance Chat Summary: 15 November 2022

The full chat log is available beginning here on Slack.

Announcements

Excellent update on the 6.1.1 release, which is going out today: 12 out of the 30 tickets in the 6.1.1 release are focused on performance! That is a great outcome and a testament to the team’s hard work on addressing some of the follow up quirks around 6.1 performance

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

@adamsilverstein:
- Been working on “Implement new experimental fetchpriority module” which hopefully can land soon
- Also working on fixing a bug with decoding="async" added in 6.1 which we fixed, and this new related ticket
- also went through the repository reviewing open issues in the Images focus
  - https://github.com/WordPress/performance/issues/470 from @pbearne looks interesting
  - https://github.com/WordPress/performance/issues/427 still needs an owner to implement SVG support
  - https://github.com/WordPress/performance/issues/354 seems like a nice addition to the dominant color feature
@mukesh27: working on fixing the focal point problem when the dominant color is enabled, ready for review
@mehulkaklotar: working on enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. PR #571 about changing default WebP quality to 82, ready for review and merge

Feedback requested

See above
Needs Discussion (10 issues)
Needs Review (5 issues)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: No updates on object caching, has been focusing on 6.1.1 and theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.
- A lot of theme.json parsing APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. have very serious performance issues
- We have fixed a couple of them and they are making the way in 6.1.1
- Another very relevant ticketticket Created for both bug reports and feature development on the bug tracker. is #57077 and #57114
@OllieJones: has a prototype of SQLite3 persistent object cache cooking; will make a module proposal soon (basically use SQLite for object caching rather than the main DB)
- @flixos90: I wonder how much that overlaps or potentially conflicts with the proposal to use SQLite as database
- @aristath: No overlap or conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved.… But they can definitely be combined for a performance boost
- @flixos90: If a site can benefit from an SQLite DB speed and we implement that feature reliably, why would you not want to use that but then use it for an object cache?
- @OllieJones: there are many installations that could benefit from a persistent object cache pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, without requiring a port of the main data to SQLite. And backup / redundancy / infrastructure would not need to change
- @flixos90: The idea sounds very useful to me especially given wider support of SQLite, but I would still like to explore a better answer on balancing this “SQLite as cache” project with the “SQLite as DB” project and the tradeoffs between the two

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Measurement

N/A

GitHub project

No updates

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

@aristath: No updates, has been working on the SQLite implementation (see Database section below) this week

Feedback requested

Needs Discussion (4 issues)
Needs Review (2 issues)

Database

@olliejones

GitHub project

@aristath: SQLite PR is ready for another round of tests and reviews
- @flixos90: reviewed it a few times and it looks excellent to me. Some quirks to still address mostly. One thing I still want to explore a bit more is trying to figure out a way to have the SQLite DB prepopulated so that you don’t end up on the WP Install screen after updating the module; this wouldn’t be a blockerblocker A bug which is so severe that it blocks a release., but it would make the user experience a whole lot smoother
- @flixos90: I would suggest we polish this over the next week and aim for a merge within the next 2 weeks? This way we can publish the first version in the upcoming Performance Lab 1.8.0 release mid December
@aristath will work on drafting a Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post on the SQLite module for once it’s in the Performance Lab plugin
- @flixos90: Best to draft it soon, so that we can review and finalize it early; this way we can publish it immediately the same day that that release will go out (December 19)

Feedback requested

Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Next Monday we’ll have the Performance Lab 1.7.0 release
- At the moment, there are still 5 PRs in the milestone which need to be committed or punted by tomorrow
- @mukesh27: PR #582 is ready for your review
  - @flixos90: Looks like that PR tackles a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. that #578 also focuses on (although that one does a bit more)
- @flixos90: Given the size of the database health checks PR, I think it’s a bit too early (or too late, if you look at it from another angle) to merge it this short before the release, also since it’s a new module
  - @OllieJones: ok. let’s puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) it; will iterate on it so maybe we can merge it in the next few weeks for 1.8.0
- @mehulkaklotar: PR #571 is under reviews right now, we will be able to merge it before tomorrow
- @pbearne: I believe they are ready but will check

Feedback requested

See above
Needs Discussion (5 issues)
Needs Review (3 issues)

Open floor

@OllieJones: I’d like to see w.org sign up for the https://greensoftware.foundation/
- @flixos90: What kind of effort or commitment does that entail? As mentioned on the issue that you opened about this, this would probably be best to move forward with a Make Core post proposing it; getting a sense of interest at a larger scale is one reason I’d propose writing a Make Core post

Our next chat will be held on Tuesday, November 22, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

Bethany Chobanian Lang 5:07 pm on November 8, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance Chat Summary: 8 November 2022

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

Mini bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub of performance issues for 6.1.1

See here
https://core.trac.wordpress.org/ticket/56923 – PR committed; should become available when @mamaduka syncs GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on Thursday
https://core.trac.wordpress.org/ticket/56815 – assigned to @flixos90 for review
https://core.trac.wordpress.org/ticket/56900 – assigned to @peterwilsoncc for commit
https://core.trac.wordpress.org/ticket/56945 – @flixos90 has PR in progress at https://github.com/WordPress/wordpress-develop/pull/3536 that needs review and feedback, especially from Gutenberg team. @annezazu working to loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. someone in there.
https://core.trac.wordpress.org/ticket/56948 – ready for commit, just needs a final review; assigned to @peterwilsoncc
https://core.trac.wordpress.org/ticket/56952 – @adamsilverstein to look into
https://core.trac.wordpress.org/ticket/56974 – @flixos90 took a first look at the PR last week and will give it a comprehensive review today
https://core.trac.wordpress.org/ticket/56990 – @adamsilverstein‘s changes need review/testing
https://core.trac.wordpress.org/ticket/56991 – @spacedmonkey‘s fix at https://github.com/WordPress/wordpress-develop/pull/3575 needs review
https://core.trac.wordpress.org/ticket/57012 – ready for commit by @peterwilsoncc

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

@adamsilverstein: Discovered a library, jSquash, that brings image format encoding/decoding to the web. Tested a bit and oping to use it to enhance the core image blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. with modern image capabilities. If successful, would let us introduce AVIF support without depending on server-side support.
@mehulkaklotar: Working on #563 for Performance Lab to change default WebP quality to 82; PR needs review.

Feedback requested

See above
Needs Discussion (10 issues)
Needs Review (5 issues)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Working mostly on 6.1.1 issues, but a few for 6.2, as well:
- https://github.com/WordPress/wordpress-develop/pull/3544
- https://github.com/WordPress/wordpress-develop/pull/3528
- https://github.com/WordPress/wordpress-develop/pull/3534
- https://github.com/WordPress/wordpress-develop/pull/3366
- https://github.com/WordPress/wordpress-develop/pull/3365
- https://github.com/WordPress/wordpress-develop/pull/3178
@tillkruess: Chatted with @johnjamesjacoby about adding a health check for the new wp_cache_supports() function to show which object caching features are supported/not supported but recommended. See https://github.com/WordPress/wordpress-develop/pull/3347. For example, get_multiple() is quite important. Any feedback on adding as a health check?
- @spacedmonkey: Now have wp_cache_supports in core that we could use and wp_cache_supports( 'get_multiple') in all options. Instead of loading all options in one cache key, load each in their own cache key and all in single call.

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Measurement

N/A

GitHub project

No updates

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (4 issues)
Needs Review (2 issues)

Database

@olliejones

GitHub project

@olliejones: Ready for a vote on https://github.com/WordPress/performance/issues/132
- Voting now open at https://github.com/WordPress/performance/issues/132#issuecomment-1307557009 through November 29
@aristath: SQLite module PR is ready for review

Feedback requested

Needs Discussion (3 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Plugin codebase is now updated to reflect our recent modifications to the focus areas per https://github.com/WordPress/performance/pull/566, thanks to @mukesh27

Feedback requested

See above
Needs Discussion (5 issues)
Needs Review (3 issues)

Our next chat will be held on Tuesday, November 15, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

#meta

Bethany Chobanian Lang 5:00 pm on November 1, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance Chat Summary: 1 November 2022

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

Announcements

@mxbclang: Upcoming time change
- US changes next week (w/c 6 November) – meeting will shift ahead by one hour to stay at our regular time, so Nov 8 meeting will be at Tuesday, November 8, 2022 at 10:00 AM EST

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

@adamsilverstein: On the AVIF front, it looks like Apple is building support right into WebKit, which means AVIFs will work on older iOSiOS The operating system used on iPhones and iPads./MacOS as long as users upgrade Safari (currently support depends on the underlying OS). See https://github.com/WebKit/WebKit/pull/5669. The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. is https://core.trac.wordpress.org/ticket/51228; the only outlier for AVIF support is now Microsoft Edge. In addition to 50%+ improvement over JPEG compression, AVIF images add support for HDR on the web; a contributor linked some sample images from the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket that are quite impressive.
@adamsilverstein: When working on the PR for setting fetchpriority=high on the non-lazy-loaded LCP image, noticed the first image on blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes isn’t having the lazy-loading attribute omitted as expected. Opened #56930 and PR #3538 to resolve; reviews appreciated. Also related: #56927, #55996.
- @spacedmonkey: Also flagging https://github.com/WordPress/gutenberg/issues/45224 as related; @adamsilverstein will add link to the Trac ticket
@mehulkaklotar: Working on some improvements to Performance Lab:
- Issue #560 – PR #565 – WebP upload configuration checkbox not showing in Settings > Media for multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site -> Merged
- Issue #563 – PR #571 – Change default WebP quality to 82
@masteradhoc: Any updates on WebP?
- @adamsilverstein: There has been some communication with Matt, repeating what he said on his post about concerns about WebP not being ready to be default mostly because it is hard to use outside of the web context. Hopefully in the future we’ll be able to get this kind of feedback earlier in a feature’s lifecycle. To move WebP further, we would need to address the underlying issue, either by improving ecosystem compatibility (which is happening naturally over time) or by improving browser capabilities (e.g. save as JPEG).
- @spacedmonkey: In multisite, we used to proxy all attachments through PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher. Could we do that here? Proxy to see if there is WebP support, and if not, return JPEG. Has its downsides but thinking out loud.
  - @adamsilverstein: Didn’t know about that; could potentially only handle “missing” images that way using htaccess
  - @spacedmonkey: It’s still part of core: https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/ms-files.php
- @masteradhoc: Could we open a ticket in the Chromium GH for save as JPEG to see if they could add? Would help the biggest part of the web.
  - @adamsilverstein: Yes, think it’s worth asking them to consider.
- @flixos90: We can’t really solve the problem in a clean way in WP though, since the right-click Save As behavior can’t be modified via PHP or JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.. Wish browsers supported some way of achieving a JPEG download of a WebP image on the web, e.g. if you use a <picture> element it could be default download as JPEG even when WebP is served in the browser. Or there could be some kind of download-src attribute.
  - @rmccue: Have run into this while serving images dynamically, no great way to handle
  - @flixos90: Looking to see if there’s anyone we can work with on this internally at Google

Feedback requested

See above
Needs Discussion (10 issues)
Needs Review (1 issue)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Tickets:
- https://core.trac.wordpress.org/ticket/56923
- https://github.com/WordPress/gutenberg/issues/45309
- https://github.com/WordPress/wordpress-develop/pull/3528
- https://github.com/WordPress/wordpress-develop/pull/3544
- https://github.com/WordPress/wordpress-develop/pull/3534
@spacedmonkey: Reviewed performance in 6.1-RC3 and updated results here; looking good. FSE themes are still slower than classic themes. Created some tickets related to issues found; have been working on https://github.com/WordPress/wordpress-develop/pull/3540.
@flixos90: Also did an analysis on RC3 last week; major improvement over RC1 and RC2. Still a few areas that were slightly worse than 6.0, but some of that is due to added functionality. Still a few quirks where regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. is noticeably worse, namely in the wp_head action. Have tracked down the particular change that makes wp_head slower even in classic themes; PR with a potential fix here: https://github.com/WordPress/wordpress-develop/pull/3536.
@spacedmonkey: Biggest issue is that class is static methods and variables, which makes it hard to review and test.

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Measurement

N/A

GitHub project

@adamsilverstein: Digging back into the testing environment work that started awhile ago to see what we can pick up and use and what an MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia could look like. Still researching/documenting, but more to come.

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JS & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (4 issues)
Needs Review (2 issues)

Database

@olliejones

GitHub project

@mxbclang: @aristath is continuing to work on the SQLite integration module in https://github.com/WordPress/performance/pull/547; feedback welcome
@spacedmonkey: Thoughts on running core unit tests against SQLite, similar to how tests are run against memcache? Could allow the tests to fail for now, but would highlight where we need to fix issues.
- @adamsilverstein: Great idea, curious about performance as well
- @spacedmonkey: Is this Trac or MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.?
- @adamsilverstein: Neither, Performance Lab only right now; proposal here
- @spacedmonkey: Yes, but add official support for testing against SQLite, so in the test run, install the drop-in for SQLite and run tests
- @adamsilverstein: I see, I think that is still core since it’s all in the main develop repo
- @spacedmonkey: Will create a ticket for this

Feedback requested

Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Planning to review https://github.com/WordPress/performance/pull/566 today, which brings the focus areas up-to-date.
@mehulkaklotar: I have worked on issue #561 – PR #570 – Investigate unexpected input Warning message during release build process -> Needs review and testing both

Feedback requested

See above
Needs Discussion (5 issues)
Needs Review (3 issues)

Our next chat will be held on Tuesday, November 8, 2022 at 10am EST in the #core-performance channel in Slack.

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

#meta

Bethany Chobanian Lang 3:38 pm on October 25, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance Chat Summary: 25 October 2022

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

Announcements

@mxbclang: Upcoming time change
- Europe changes w/c 30 October before US does – Nov 1 meeting will be one hour later at Tuesday, November 1, 2022 at 12:00 PM EDT
- US changes w/c 6 November – meeting will shift ahead by one hour to stay at our regular time, so Nov 8 meeting will be at Tuesday, November 8, 2022 at 10:00 AM EST

Focus area updates

@mxbclang: Results of focus area updates vote
- Added new Database focus area – see GH label and Project
- Renamed JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. focus area to JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets. – see GH label and Project
- Removed Site Health focus area – added “LEGACY” to GH label and Project and moved all active issues to an appropriate new focus area
- Working on adding a list of focus areas to the Handbook
- Call for leads for Database – @olliejones volunteered! Will update GH accordingly

Images

@adamsilverstein @mikeschroder

GitHub project

@mxbclang: Working on changing the image quality for WebPs in Performance Lab from 86 to 82: https://github.com/WordPress/performance/issues/563
@pbearne: Will investigate https://github.com/WordPress/performance/issues/562 this week

Feedback requested

See above
Needs Discussion (10 issues)
Needs Review (1 issue)

Object Cache

@tillkruess @spacedmonkey

GitHub project

No updates

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Measurement

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
@mxbclang: Work continuing on defining the PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Checker plugin and getting close to engineering; more updates soon

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JS & CSS

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (4 issues)
Needs Review (2 issues)

Database

@olliejones

GitHub project

No updates

Feedback requested

Needs Discussion (2 issues)
Needs Review (2 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Planning to get back to the Server-Timing APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. work this week and reviewing focus area updates in https://github.com/WordPress/performance/pull/566 today

Feedback requested

See above
Needs Discussion (6 issues)
Needs Review (3 issues)

Open Floor

@flixos90: Identified and validated the main cause of the regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. with @spacedmonkey and it has been fixed. Will run another iteration of the same analysis for 6.1-RC3 today or tomorrow to verify that results have improved.
- @olliejones: What was it?
- @flixos90: Was caused by a bug in https://core.trac.wordpress.org/ticket/39210. Research has not yet been published as wanted to see how the situation evolves, but fair to say that we got the perfect outcome and it shows how important performance analyses are. Will write a summary with concrete numbers up next week and publish after 6.1 launch.

Our next chat will be held on Tuesday, November 1, 2022 at 12pm EDT in the #core-performance channel in Slack.

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

#meta

Bethany Chobanian Lang 4:06 pm on October 18, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance Chat Summary: 18 October 2022

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

Announcements

@mxbclang: Reminder: Focus area updates vote and call for leads
@mxbclang: Upcoming time change
- Europe changes w/c 30 October before US does – Nov 1 meeting will be one hour later at Tuesday, November 1, 2022 at 12:00 PM EDT
- US changes w/c 6 November – meeting will shift ahead by one hour to stay at our regular time, so Nov 8 meeting will be at Tuesday, November 8, 2022 at 10:00 AM EST
@mxbclang: New Handbook on our CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Performance site
- Some new content, some ported over from the /docs folder of the Performance Lab pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. If you have changes or updates, please contact Bethany directly; workflow for updates to come.
- @flixos90: All new documentation related to Performance Lab should go into this Handbook, not /docs as that folder has been removed

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

@flixos90: Found a bug during yesterday’s release party where the WebP upload configuration checkbox is not displaying in Settings > Media on multisites
@joegrainger: #527 and #537 we’re part of the 1.6.0 release yesterday, which bring us to parity with the planned WebP implementation in core

Feedback requested

See above
Needs Discussion (9 issues)
Needs Review (1 issue)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Just committed https://github.com/WordPress/wordpress-develop/commit/7b176e6deaeb54249f7096c8ef8415d3edb46e39
@spacedmonkey: Spent some time testing RC2 and seeing better numbers for page performance than for Beta2. Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. appears to have come from a change to PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher related to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. Numbers are better than Beta2 but not as good as 6.0 – 0.6325s for Beta2, 0.4014s for RC2, and 0.2929s for 6.0.
- @flixos90: We’ve been working on a separate performance analysis comparing 6.1 RC1 to 6.0 and will follow up today to do RC2. Unfortunately results haven’t been looking as good as 6.0 in our analysis, either. Hopefully RC2 is improving in our tests, too.
- @spacedmonkey: Have been using Blackfire for testing. You can get a free open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. license; if anyone is interested, can help them get set up.
- @flixos90: Been using WebPageTest in combination with custom-measured Server Timings, so these two analyses can complement each other well.
- @spacedmonkey: Don’t think we will have time to fix these issues before 6.1 release; these would require big changes so doesn’t feel like a good idea to get merges committed without testing. Maybe possible for 6.1.1.
- @aristath: Been using Xdebug and webgrind and pushed a few tweaks to core in the last few weeks as the result of those tests. Setup instructions are here if anyone’s interested in getting started easily.
- @johnbillion: For anyone who wants timing information and doesn’t have access to Xdebug/Cachegrind/XHProf/Blackfire etc., you can do rough timing with the Query Monitor plugin
- @spacedmonkey: One issue I’ve found is that a lot of code related to theme.json is being loaded even if the active theme does not support these features
- @mukesh27: Agreed
- @spacedmonkey: Would like to work on conditionally loading these features on classic themes; much of this has been an issue since 5.9
- @johnbillion: There are a few issues on that topic in the Gutenberg repo, e.g. https://github.com/WordPress/gutenberg/issues/38299

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Site Health

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
@mxbclang: Yesterday’s Performance Lab release included functionality to only load the two new SH checks that will be in 6.1 (persistent cache and full page cache) when they are not available in core: https://github.com/WordPress/performance/pull/543

Feedback requested

Needs Discussion (8 issues)

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

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Got 4 non-critical debug warnings during the release deployment yesterday, which we should look into: https://github.com/WordPress/performance/issues/561
@flixos90: Want to highlight the Server-Timing API proposal again. Been working on a proof of concept in https://github.com/WordPress/performance/pull/553 which would be great to get some first reviews on. Also added some example usage code and linked a Gist with several examples for how we could leverage that APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to expose specific timings. Exact API seems a bit clunky to use and already have some ideas on how to simplify it better to fit the usage. Still works well technically though, so it’s okay to be reviewed.

Feedback requested

See above
Needs Discussion (6 issues)
Needs Review (3 issues)

Module proposal: SQLite – @aristath

@mxbclang: Related to the broader proposal to make WP officially support SQLite
@aristath: The SQLite implementation can be found on the PR linked above. A couple of minor issues with the implementation, but they don’t have anything to do with the SQLite code itself. The issues I have in that PR are related to the module’s activation and deactivation: when enabling/disabling the module, WP switches DBs and subsequently all options regarding the activation/deactivation of the module are difficult to handle because on option-save, we switch databases. It’s a solvable UXUX User experience issue, but could definitely use some assistance. At this stage, believe it’s time to start collaborating on the PR, test it, and merge relatively early so we can urge more people to test.
@flixos90: Re-sharing one idea mentioned when discussing this previously (see Slack): Present a warning that this will result in an empty DB. If the user clicks Activate, show a modal where they have to enter SQLite config data, then put that into wp-config.php and install the DB before they activate. This way, they could remain on the same screen and continue to use WP or deactivate if they want to. Would avoid an overly confusing experience.
@aristath: Added a note next to the module (not a modal). SQLite doesn’t currently require any user-provided config, so didn’t want to make things more complicated. Agree that we should have something more user-friendly and be clear about what will happen and why.
@flixos90: So there would not be any constant to add to wp-config.php?
@aristath: At this stage, no – the module automatically copies a db.php file in wp-content, assuming that if the file is there, you want to use SQLite. On deactivation of the module, the file is deleted so you go back to your MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. database.
@flixos90: There are other use-cases for db.php, though, so wary of the existence of the file being the only thing that we rely on. Should probably also back up any existing db.php file in case and restore it on deactivation of the module.
- @rickjames: Will there be a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. path from SQLite to MySQL? Thinking of a case where someone starts out with a “small” site but it grows “too big” for SQLite
  - @aristath: If SQLite is included in core, there will definitely be a migration path. Most likely it would be in the form a canonical plugin and not core. Don’t think it will be the nightmare we envision it to be – just connect both DBs and copy data between them.
- @aristath: If they have a different db.php file, then they’re already using a custom DB somehow – if it’s detected, the module does not overwrite and instead exits
@rickjames: Don’t think there is any way to keep the DBs “in sync”
- @aristath: There is a way, but wouldn’t want to do it. This is intended to be a module to test the stability of SQLite in WP and work toward implementation in core. Not intended to take care of syncing dbs, using them to back up data, etc.
@mxbclang: Feel free to leave comments on https://github.com/WordPress/performance/pull/547 and we can always discuss this further in a future chat, as well

Our next chat will be held on Tuesday, October 25, 2022 at 11am EDT in the #core-performance channel in Slack.

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

#meta

Bethany Chobanian Lang 4:19 pm on October 11, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance team meeting summary 11 October 2022

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

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

@adamsilverstein: Committed two small fixes related to the existing `image_editor_output_format` filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. – #54476 and #56442
@mukesh27: Added checkbox to Settings > Media to control whether to generate JPEG in addition to WebP in #537
- @flixos90: This is unlikely to ever make it into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but it is useful in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to test either of the two behaviors
@ankitgade: Continuing to work on background processing infrastructure
- Background process runner class PR is up for review: https://github.com/WordPress/performance/pull/512
- Working on job status check cron: https://github.com/WordPress/performance/pull/552
- Working on adminadmin (and super admin) queue screen: https://github.com/WordPress/performance/pull/533

Feedback requested

See above
Needs Discussion (9 issues)
Needs Review (1 issue)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Published and helped with several dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1:
- https://make.wordpress.org/core/2022/10/10/performance-improvements-to-the-rest-api/
- https://make.wordpress.org/core/2022/10/10/multisite-improvements-in-wordpress-6-1/
- https://make.wordpress.org/core/2022/10/07/improvements-to-wp_query-performance-in-6-1/
- https://make.wordpress.org/core/2022/10/06/new-cache-site-health-checks-in-wordpress-6-1/
- https://make.wordpress.org/core/2022/10/11/performance-field-guide-for-wordpress-6-1/
@spacedmonkey: Also merged https://github.com/WordPress/wordpress-develop/pull/3424 and https://github.com/WordPress/wordpress-develop/pull/3403 and need code review for https://github.com/WordPress/wordpress-develop/commit/832b6c35f36d5f1ca84feadc49b0e5424af0ad6c, which will add a new function to core called wp_cache_supports to allow object caches to support different functionality
@spacedmonkey: Been investigating the performance regression seen in Beta 2, particularly new caching issues in block themes – see https://github.com/WordPress/gutenberg/issues/44772 for details. PR in the works https://github.com/WordPress/wordpress-develop/pull/3418 that needs review ASAP before the RC1 cutoff.

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Site Health

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
@mxbclang: Dev note for new Site Health checks has been published: https://make.wordpress.org/core/2022/10/06/new-cache-site-health-checks-in-wordpress-6-1/

Feedback requested

Needs Discussion (8 issues)

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

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Our next release, 1.6.0, will be this coming Monday, October 17. Any feature or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. that you want to include in this release should be completed and merged by tomorrow (Wednesday, October 12, see #548).

Feedback requested

See above
Needs Discussion (6 issues)
Needs Review (3 issues)

Focus area updates

@flixos90

@flixos90: Three proposed changes that have come up in recent weeks to align focus areas. First is to introduce a new Database focus area; there are several module proposals (SQLite, optimized autoloaded options, database health checks) and some core optimizations that would also fit into this
- @spacedmonkey: Should Object Caching and Database be the same?
- @olliejones: Suggest keeping them separate
- @flixos90: Don’t think so, some are pure database optimizations while sometimes object caching works around DB requests. I’d say adding caching around DB queries is still “Object Caching,” but there’s also room to improve some queries themselves and other DB issues
- @spacedmonkey agrees
@flixos90: Second: We have a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. focus, but there’s also a lot of work going on in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ to improve CSSCSS Cascading Style Sheets. loading. Should we introduce a CSS area, or alternatively broaden the existing focus to be Assets (including CSS & JS)?
- @mxbclang: Makes sense to me to broaden JS to both unless we have someone who is really interested in leading CSS
- @spacedmonkey: Think they should be separate; if no one leads CSS, then it is not a “focus”
- @mxbclang: That’s not entirely true; there’s some maintenance around designating something as a “focus,” e.g. having it on our weekly agenda, GH labels, updating the CODEOWNERS file, etc.
- @olliejones: Is the scope of the JS focus intended to cover ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. apps and XHR/fetch performance?
- @flixos90: FWIW the JS focus has barely made any updates here since it was established, but it’s a noticeable aspect of performance and some projects have been kicked off so would not want to remove it; @aristath has been quite involved with CSS though
- @spacedmonkey: What does the JS focus mean right now?
- @adamsilverstein: We do have some work around enabling better loading strategies for scripts that falls under JavaScript; I’ve been working on researching the benefits of using defer
- @flixos90: Generally most of our focus is on website front-end performance, so the JS focus is also focused on front-end – things like deferring scripts, not loading JS that isn’t used, etc.
- @spacedmonkey: How about a “Front-End” focus then?
- @flixos90: Don’t think that would make sense, since everything we do is about front-end. Even DB queries and object caching improvements affect the front-end a lot. Let’s discuss later.
@flixos90: Last one: Suggest removing the Site Health focus – not because we shouldn’t work on Site Health, but more because any Site Health check actually fits into other areas and would be better suited as part of the other focus areas as opposed to it’s own area. There has not been a focus lead for Site Health, which is maybe another indicator that we should retire this area and consider checks to be part of other focus areas moving forward.
- @spacedmonkey: So like an object caching-related Site Health check would be part of the Object Caching focus, right? Yes
- @flixos90: Looking at our current SH modules:
  - Autoloaded options audit > Database
  - Enqueued assets > JS/CSS (TBD)
  - Full page cache > Object Caching
  - WebP support > Images
Vote on all through proposals here through Tuesday, October 18, 2022 at 1pm EDT: https://github.com/WordPress/performance/issues/554

Our next chat will be held on Tuesday, October 18, 2022 at 11am EDT in the #core-performance channel in Slack.

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

#meta

Bethany Chobanian Lang 4:02 pm on October 4, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance team meeting summary 4 October 2022

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

Announcements

@mxbclang: Mission and philosophies review
- Drafting a Handbook for our site and would like to include overall mission for the team
- Please review and leave comments on the doc with your thoughts

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

@adamsilverstein: Not much to update, worked on a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fix for #56442
@eugenemanuilov: #524 to disable JPEG subsizes generation for WebP images has been updated based on feedback from @flixos90
@mukesh27: Working on #525 to add a checkbox to the Media screen to enable multi-MIME type output, to match with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. WebP implementation
@ankitgade: Working on background processing infrastructure related to image regeneration
- Background job class PR #507 is merged
- Background process runner PR is in progress and will be ready to review tonight
- Adminadmin (and super admin) queue screen PR is work in progress
@khoipro: Any updates on SVG uploads?
- @mxbclang: No one is actively working on this at the moment, so anyone can pick it up if they have time https://github.com/WordPress/performance/issues/427
- @spacedmonkey: Not working on this right now, but may in the future. Biggest blockerblocker A bug which is so severe that it blocks a release. is that the library that everyone uses for cleaning SVGs requires PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 7+, so it would need to be forked/rewritten if we wanted backwards compatibility. If we wanted to make it a PHP 7+-only feature, it would make things a lot easier.
- @flixos90: WP hasn’t really done that before, but don’t think it’s a no-go as long as it’s a non-critical feature
- @spacedmonkey: PHP 5.6 is only 4% of WP installs, per https://wordpress.org/about/stats/
- @adamsilverstein: We already do something like this with server support for images where you can’t use a format unless your server supports it
- @flixos90: As long it gracefully falls back if unsupported and doesn’t break anything on older versions, would be totally onboard
- @khoipro: What about sanitize and escape file uploading, and styling SVG in media preview?
- @flixos90: Matt also mentioned a few years back that he would be open to WP offering certain features only to sites with HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information., kind of similar
- @spacedmonkey: The creator of the library was open to support, not sure how much work we would need to do to port back to 5.6
- @flixos90: Unless backporting would be super straightforward, I would say it’s not worth our effort and we make it 7+ only
- @ankitgade: We can analyze what issues we see on 5.6 to evaluate how difficult this would be

Feedback requested

See above
Needs Discussion (9 issues)
Needs Review (2 issues)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Committed https://core.trac.wordpress.org/ticket/56721 and need review and commit on https://github.com/WordPress/wordpress-develop/pull/3403
@spacedmonkey: Also been profiling and testing WP 6.1 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2 – profiling data
- @spacedmonkey: WP6.1 beta 2 has a slower page generation time than 6.0, in some cases by a lot (0.6325 vs. 0.2929 seconds), even with fewer DB calls in a lot of cases
- @flixos90: Did you test 1 for each scenario, or multiple and then use average/median results?
- @spacedmonkey: Ran at least three times and did median
- @flixos90: If we could automate, maybe do something like 5-10 runs to make it more accurate
Also working on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. (1, 2, 3) – @mxbclang has reviewed and @flixos90 will take a look today or tomorrow
@khoipro: Will assign someone from their back-end team to take a look at profiling and testing, as well

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Site Health

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
@furi3r: Draft Make post is in progress for the new SH checks in 6.1, waiting for a final review before publishing

Feedback requested

Needs Discussion (8 issues)

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
@mxbclang: Getting closer to starting engineering on the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party performance checker thanks to @mehulkaklotar and @jjgrainger‘s work on a design doc

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath @sergiomdgomes

GitHub project

No updates

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@flixos90: Per the vote to bump the Performance Lab plugin minimum requirement to WP 6.0, our next release will require 6.0
@flixos90: Our next release, 1.6.0, will be Monday, October 17, less than two weeks from now. Any feature or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. that you want to include in this release should be completed and merged by next Wednesday, October 12 (see #548).

Feedback requested

See above
Needs Discussion (6 issues)
Needs Review (3 issues)

Module proposal: Server-Timing API

@flixos90

@rickjames: For server-side performance measurement, MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/.’s “slowlog” can be useful
@flixos90: Not familiar with that tool, but worth exploring another time and feel free to draft a proposal. The current proposal leaves the actual measurement agnostic so it would leave room to introduce a more flexible and opinionated system later.
@adamsilverstein: Overall love the proposal, are you proposing that this would be included in the response by default once this is added?
- @flixos90: Yes, envision that it would be added by default
@johnbillion: Added a comment on the issue about headers: headers need to be sent before any output, and a lot of processing that happens in WordPress that would ideally be measured occurs after the output begins
- @flixos90: Definitely a fair point. Even with that limitation, still a lot of benefit to having the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. to measure everything until WP begins to render the output. This will be a known limitation eventually, but also think this will become a smaller issue with FSE sites because they typically generate all content and then it is just “printed” out, so less “work” happening after headers are sent.
- @johnbillion: Maybe, but <head> still gets filled up by plugins and core doing processing. Would be good to think of what metrics would be useful to see and whether exposing those metrics via this APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. makes sense.
- @flixos90: One example would be the autoloaded options query given the recent module proposal to improve that
- @johnbillion: Does FSE actually construct its output before it’s all sent?
  - @aristath: Yes, the whole content/template gets rendered internally prior to sending any headers
- @johnbillion: Like the idea of using the Server-Timing API header, but not sure if it necessarily works for WP
- @flixos90: Isn’t it worth pursuing to be able to cover anything that happens prior to page output, which is a lot?
- @johnbillion: It could well be, but would be good to see real world examples of what would be good to measure. Output buffering may not be the worst idea if the API is restricted to the plugin; definitely worth investigating.
- @flixos90 will think about examples

Open floor

@aristath: Started porting SQLite as a module: https://github.com/WordPress/performance/pull/547; will discuss further next week
@josklever: https://core.trac.wordpress.org/ticket/55344 is related to the performance of the WP dashboard. Resources are loaded for dashboard widgets that are disabled via Screen Options, which can cause unwanted delays or issues for other widgets if there are conflicts.

Our next chat will be held on Tuesday, October 11, 2022 at 11am EDT in the #core-performance channel in Slack.

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

#meta

Bethany Chobanian Lang 3:56 pm on September 27, 2022
Tags: core-js, core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 144 ), performance-chat ( 109 ), summary ( 632 )

Performance team meeting summary 27 September 2022

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

Announcements

@mxbclang: Mission and philosophies review
- Drafting a Handbook for our site and would like to include overall mission for the team
- Please review and leave comments on the doc with your thoughts

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

@spacedmonkey: Need dev notes for https://core.trac.wordpress.org/ticket/53232
- @mxbclang: Will work with Adam to see if he can pick this up
@eugenemanuilov: Worked on #524 to disable JPEG subsizes generation for WebP images; #525 also in progress and almost ready for CR
@ankitgade: Working on background processing infrastructure related to image regeneration
- 1. Job class PR is awaiting review: https://github.com/WordPress/performance/pull/507
  2. Background process runner PR is in draft as it has dependency on #507: https://github.com/WordPress/performance/pull/512
  3. Adminadmin (and super admin) queue screen PR is in progress: https://github.com/WordPress/performance/pull/533
@mxbclang: No updates on next steps on WebP just yet; discussions still ongoing

Feedback requested

See above
Needs Discussion (9 issues)
Needs Review (2 issues)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Working on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1
- Improvements to WP_Query – https://docs.google.com/document/d/1_D3_J1BwWQ8_zpc7TWWypR-29dHC6l7HZ7eNX0eeMZs/edit?usp=sharing
- Improvements to multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site –https://docs.google.com/document/d/1EFKmDd97jo0St9bIMZ82EDFd2_mDfDEheJ3VuVJUUG0/edit?usp=sharing
  - https://core.trac.wordpress.org/ticket/37181
  - https://core.trac.wordpress.org/ticket/55802
- Site Health –https://docs.google.com/document/d/11ekflhRTZjxwuXBBDBcvvrRNDL0Gy2NobsuKrHSXdb8/edit?usp=sharing
  - https://core.trac.wordpress.org/ticket/56040
  - https://core.trac.wordpress.org/ticket/56041
  - @mxbclang: Mostly ready to go; waiting for @furi3r to return and publish
- Performance improvements to REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.
  - https://core.trac.wordpress.org/ticket/55677
  - https://core.trac.wordpress.org/ticket/55620
  - https://core.trac.wordpress.org/ticket/55674
  - https://core.trac.wordpress.org/ticket/52992
  - https://core.trac.wordpress.org/ticket/56272
  - https://core.trac.wordpress.org/ticket/55592
  - https://core.trac.wordpress.org/ticket/55716
  - https://core.trac.wordpress.org/ticket/56019
  - https://core.trac.wordpress.org/ticket/56020
  - Can @tillkruess work on this dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.?
- Improvements to caching APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
- Script improvements
  - https://core.trac.wordpress.org/ticket/42438
- Images
  - https://core.trac.wordpress.org/ticket/53232
- @zzap will help with doc review
- Want to make sure that these changes are listed in the field notes and on the 6.1 about page, since they weren’t included on the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 announcement blogblog (versus network, site)
  - Changes like added caching to WP_Query have a big impact and need to be called out
  - @zzap: These will all be added to the field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Site Health

N/A

GitHub project

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
No updates

Feedback requested

Needs Discussion (8 issues)

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
@robinwpdeveloper: Incorrect message about the status of WP_AUTO_UPDATE_CORE #51041 was committed today

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath @sergiomdgomes

GitHub project

@aristath: No movement on the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. front recently, so focusing on general performance improvements instead, including #56636, #56637, #56654 and just a few minutes ago #56666. The process I’ve been following is to basically run vanilla WP using Xdebug-profiling, examine the results using webgrind and try to reduce the amount of function calls – as well as their cost. Generally small tweaks, with relatively big benefits. Last week #55005 was also merged in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so overall I believe WP 6.1 contains a lot of nice and impactful performance changes – as highlighted by all the updates from other folks above.

Feedback requested

Tree-shaking block styles on the frontend #41020
Needs Discussion (2 issues)
Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

@mxbclang: Vote about bumping minimum requirement to WP 6.0 open through this Friday; please vote if you haven’t already
@mukesh27: Add JavaScript coding standard workflow #515 and Update @wordpress/env to latest version #546 need review

Feedback requested

See above
Needs Discussion (5 issues)
Needs Review (3 issues)
Needs Decision (1 issue)

Discussion: SQLite support

@spacedmonkey and @aristath

@spacedmonkey: Think this is a great idea and could be useful in core for running unit tests and for other projects like wordpress-wasm. Wonder if the performance team should help take on this problem, even if it is to review the solution and ensure that there’s no performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5..
@aristath: Understand that testing could be difficult, so currently converting it to work as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party in this repository. Trying to convert to something that would make sense for core and then publish in the .org repo as a featured plugin. Hoping if this is in the form of the plugin, more people will test and provide feedback. Also noting that the initial proposal focused on small-to-medium sites, but there’s great potential for growth in other areas as well where large sites can take advantage of SQLite.
- @spacedmonkey: I’ve forked hyperdb and run very large multisites, can provide context here
- @aristath: We’ll need lots of context once we get rolling – the prospect of pairing SQLite and hyperdb is very exciting

Our next chat will be held on Tuesday, October 4, 2022 at 11am EDT in the #core-performance channel in Slack.

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

#meta

Welcome!

Communication

Focus area updates

Images

Feedback requested

Object Cache

Feedback requested

Measurement

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

Feedback requested

Database

Feedback requested

Infrastructure

Feedback requested

Open floor

Announcements

Focus area updates

Images

Feedback requested

Object Cache

Feedback requested

Measurement

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

Feedback requested

Database

Feedback requested

Infrastructure

Feedback requested

Open floor

Announcements

Focus area updates

Images

Feedback requested

Object Cache

Feedback requested

Measurement

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

Feedback requested

Database

Feedback requested

Infrastructure

Feedback requested

Open floor

Focus area updates

Images

Feedback requested

Object Cache

Feedback requested

Measurement

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

Feedback requested

Database

Feedback requested

Infrastructure

Feedback requested

Announcements

Focus area updates

Images

Feedback requested

Object Cache

Feedback requested

Measurement

Feedback requested

JS & CSSCSS Cascading Style Sheets.

Feedback requested

Database

Feedback requested

Infrastructure

Feedback requested

Announcements

Focus area updates

Images

Feedback requested

Object Cache

Feedback requested

Measurement