Page MenuHomePhabricator

[26Q2] Orchestrator memory squashing
Closed, ResolvedPublic

Description

Hypothesis:
If we can prevent 10x memory consumption spikes, the orchestrator will be better able to handle Wikidata objects, supporting the utility of Wikifunctions as a platform for Abstract Wikipedia.

Acceptance Criteria

  • At least 2–3 spike investigations into root causes orchestrator crashes and implement at least one intervention to improve memory consumption
  • Share findings about memory usage among the team to steer work
  • Thrice-weekly pair programming

Goals & Success Metrics

  • Node's GC memory usage is well understood and does not spike beyond service's memory limits
  • Ability to process 10 large Wikidata items in a single function call without crashing
  • 3 further engineers are Certified Orchestrator Whisperers for the orchestrator and can participate in hypothesis work involving its performance

Related Objects

Event Timeline