Skip to content

[testcore] Use a single shared cluster for everything#10979

Draft
long-nt-tran wants to merge 1 commit into
temporalio:mainfrom
long-nt-tran:singular-shared-cluster
Draft

[testcore] Use a single shared cluster for everything#10979
long-nt-tran wants to merge 1 commit into
temporalio:mainfrom
long-nt-tran:singular-shared-cluster

Conversation

@long-nt-tran

@long-nt-tran long-nt-tran commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

What changed?

Experiment to try and see if we can reuse a single shared cluster for all tests that request a shared cluster.

Why?

Reduce memory usage of tests.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

Potential risks

Need to watch out if it increases flakes.

stephanos added a commit that referenced this pull request Jul 9, 2026
Combine with the worker-enabled-by-default experiment: keep the system
worker on for all pooled clusters, but shrink the shared pool to a single
cluster so far fewer clusters run concurrently. Measures whether the
single-shared-cluster change offsets the worker's memory impact.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@long-nt-tran long-nt-tran force-pushed the singular-shared-cluster branch from a90573e to be31227 Compare July 9, 2026 15:33
@long-nt-tran long-nt-tran force-pushed the singular-shared-cluster branch from be31227 to cb5ef17 Compare July 9, 2026 15:43
@stephanos stephanos added the test-all-dbs Request PR checks to test all databases label Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test-all-dbs Request PR checks to test all databases

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants