temporalio / temporalio/omes

Scenario request: Continue as new on workflow with lots of events

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
102
Forks
29
Avg merge
1d 22h
Merged PRs (30d)
22

Description

Describe the scenario you'd like

Run <workflow-count> workflows that generate <event-count> events (sequential activities with fake input/output payload, combine with some fake signals for example) and then continue as new. The workflow should do this event-build-and-continue-as-new <continue-as-new-iterations> times. May want to break up events with only so many in a single task instead of all in one.

The variables can be set based on good numbers that stress the environment.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the existing workflow scenario and load-generation entry points, then determine suitable stress values for workflow count, event count, and continue-as-new iterations. Done means the scenario can generate the requested events, optionally split them across tasks, and continue as new repeatedly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
performance, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.