Request for parser performance metrics
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	awight
	Jan 13 2023, 1:11 PM

Description

As part of T326317, we looked for ways to monitor the legacy (non-Parsoid) parser and its cache, and found a few shortcomings worth mentioning. These are some metrics we'd like to see, and if others approve perhaps we can start implementation:

Timing for wikitext parse
- Wall time
- CPU time
- Outliers such as P95, P99...
Breakdown of the source of parse requests (eg. API, pageview, ...)
Size of a typical parser cache entry
- Average size
- Outliers such as P99
Timing to save a page

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open		None	T326953 Request for parser performance metrics
		Open		None	T326637 Generate metrics for page saving and parsing times, to monitor impact of map external data expansion

Event Timeline

awight created this task.Jan 13 2023, 1:11 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 13 2023, 1:12 PM

awight updated the task description. (Show Details)Jan 13 2023, 1:12 PM

awight added a subtask: T326637: Generate metrics for page saving and parsing times, to monitor impact of map external data expansion.

Izno subscribed.Jan 13 2023, 11:15 PM

Hi @awight
In the performance team, we can readly address your last bullet point:
the time it takes to save a page is measured by the saveTiming metric. You can find the graphs in our grafana dashboards

The Content Transform Team might be better positioned to point you to any existing metrics they track for your specific use case.

larissagaulia moved this task from Inbox, needs triage to Radar on the Performance-Team board.Jan 16 2023, 8:33 PM

larissagaulia edited projects, added Performance-Team (Radar); removed Performance-Team.