Skip to content

[Ford] Measured Workflow publish latency on Core's store. - #169

Closed
moetemp wants to merge 8 commits into
moe/ford/w6-workflow-docsfrom
moe/ford/w7-workflow-bench
Closed

moetemp wants to merge 8 commits into
moe/ford/w6-workflow-docsfrom
moe/ford/w7-workflow-bench

Conversation

@moetemp

@moetemp moetemp commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

What changed?

This PR adds the Workflow publish scenario to the local benchmark.

  • perf04-workflow measures PERF-04 from the publish call in Workflow code to the reader's receipt.
  • RESULTS.md keeps its runs. With no persistence a Workflow publish reached p50 3.2 ms.

Why?

Core appends a Workflow's records when the activation that published them completes, so the latency should be close to an Activity append's. The run shows it.

How did you test it?

Link to a test plan if any -

  • Unit Tests
  • Staging
  • End to End Tests

Every scenario in RESULTS.md ran locally against Redis and the dev server.

@moetemp moetemp added the skip-changelog Changelog entry rides another PR label Oct 13, 2026
@moetemp moetemp added the parked Parked design, not for review label Oct 14, 2026
@moetemp

moetemp commented Oct 14, 2026

Copy link
Copy Markdown
Owner Author

Closed. The Ford project (Core Workflow Task publish) is dropped. Brook now publishes from a Workflow through a local activity, with no Core change. Bridge moves onto Brook in the coming Jetty re-cut. This branch stays until then, because Bridge PRs still sit on it.

@moetemp moetemp closed this Oct 14, 2026
@moetemp
moetemp deleted the moe/ford/w7-workflow-bench branch October 14, 2026 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

parked Parked design, not for review skip-changelog Changelog entry rides another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant