Repository navigation
Conversation
3 tasks
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
This PR adds the Workflow publish scenario to the local benchmark.
perf04-workflowmeasures PERF-04 from the publish call in Workflow code to the reader's receipt.RESULTS.mdkeeps 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 -
Every scenario in
RESULTS.mdran locally against Redis and the dev server.