Skip to content

Each fan-out member's task still rebuilds its run's whole summary #1240

Open

Description

@rmcdaniel

Follow-up to #1231 and #1203 (fixed for workflow tasks in #1235).

After #1235, a fan-out's workflow tasks are linear in width. Each member's own task still rebuilds its run's whole summary, wait, timeline and activity view from the whole run, once for the activity start, once for the activity outcome, and once for a child closure (RunSummaryProjector::project). That makes each member task O(N), so completing all members of an N-member all() is O(N²) in total. On SQLite with 1 KB arguments, it costs about 1.4 s per activity task at 300 members. Every member task fits the job timeout, but a 1,000-member fan-out does not complete in seconds.

Required outcome: an activity start, an activity outcome, and a child closure inside an open parallel group refresh the summary, waits and timeline with work that does not grow with the group's width. Projection rows must stay identical to a full projection; a test should compare them after every member transition. The 300 vs 30 member probe in tests/Support/FanOutWidthProbe.php should then pass with refreshMemberProjections: true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions