Page MenuHomePhabricator

[EPIC] Support dependency de-duplication of Codex components in ResourceLoader
Open, Needs TriagePublic

Description

Background

There may be situations where Codex components are unnecessarily loaded multiple times on the same MediaWiki page, resulting in degraded performance. This is a known consequence of the way code splitting of Codex components in ResourceLoader was implemented as part of T349423.

A number of different solutions to this problem have been explored in T343141, T350052, and T350056.

In T350056#9552797, it was decided that more prototyping would be needed before committing to an approach, so this work was split out of T349423.

Open Questions

  • What are the prime use cases motivating the need for this?
  • How much does performance actually degrade?

Event Timeline

CCiufo-WMF removed a project: Epic.
CCiufo-WMF added a project: Epic.
CCiufo-WMF moved this task from Inbox to Infrastructure on the Codex board.

What are the prime use cases motivating the need for this?

As pointed out in T378638 we are increasingly loading CSS/JS unnecessarily as we adopt Codex more. This impacts performance e.g. requires lower end devices to download and process CSS and JS that it already has in memory.

As pointed out in T378638 we are increasingly loading CSS/JS unnecessarily as we adopt Codex more. This impacts performance e.g. requires lower end devices to download and process CSS and JS that it already has in memory.

Is there a threshold at which point this becomes unacceptable? We always knew we'd have to come back to this, it was just a matter of when.