Investigate front end saving timing regression starting April 20, 2019
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	aaron
	Jun 17 2019, 4:59 PM

Description

Possibly caused by some template or module change on a group 2 wiki (enwiki?).

Related Objects

Mentioned Here: T226785: Phase out use of vary-revision with more specific flags and improve related logging

Event Timeline

aaron created this task.Jun 17 2019, 4:59 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 17 2019, 4:59 PM

Aklapper renamed this task from Investigate front end saving timing regression starting 4/20/2019 to Investigate front end saving timing regression starting April 20, 2019.Jun 17 2019, 5:18 PM

• Gilles moved this task from Inbox, needs triage to Doing (old) on the Performance-Team board.Jun 17 2019, 8:03 PM

Seems to be resolved, likely by vary-revision refactoring from T226785.

There is still one patch coming out this train for self-transclusions, but it seems mostly back to normal.

	F30052761: graph.png
	Aug 21 2019, 5:47 PM

	F29593763: save timing.png
	Jun 17 2019, 4:59 PM

Investigate front end saving timing regression starting April 20, 2019Closed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Investigate front end saving timing regression starting April 20, 2019
Closed, ResolvedPublic
Actions