Skip to content

Add cost optimization best practices guide#4174

Open
bechols wants to merge 3 commits intomainfrom
bechols/cost-optimization-guide
Open

Add cost optimization best practices guide#4174
bechols wants to merge 3 commits intomainfrom
bechols/cost-optimization-guide

Conversation

@bechols
Copy link
Contributor

@bechols bechols commented Jan 31, 2026

Adds guide covering Actions and Storage optimization strategies for Temporal Cloud.

🤖 Generated with Claude Code

┆Attachments: EDU-5853 Add cost optimization best practices guide

@bechols bechols requested a review from a team as a code owner January 31, 2026 22:13
@vercel
Copy link

vercel bot commented Jan 31, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Feb 5, 2026 3:28pm

Request Review

@github-actions
Copy link
Contributor

github-actions bot commented Jan 31, 2026

📖 Docs PR preview links

Passing multi-megabyte payloads through Workflows when external storage (S3, blob storage) is more appropriate.
Use [compression](/troubleshooting/blob-size-limit-error#why-does-this-error-occur) or the claim check pattern for large data.

### Over-optimization at the expense of observability
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we provide an example here? What kind of optimization would harm visibility?


**High Actions costs generally indicate**:

- Many Activities per Workflow
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


Each Activity retry counts as 1 Action.
Default [Retry Policies](/encyclopedia/retry-policies) can be aggressive, which is appropriate for most operations but costly for expensive external operations.
Consider limiting maximum attempts, increasing initial intervals, and using larger backoff coefficients for expensive operations while maintaining standard retry behavior for normal operations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We haven't used many examples in this guide, but it feels like one would really help here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants