Skip to content

Conversation

@mikenomitch
Copy link
Contributor

Summary

Adds changelog entry and tweaks docs for allowing cpu_ms to go up to 5 minutes.

@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Mar 24, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Updated documentation to reflect an increase in CPU time limits for Workers.

  • Added a changelog entry for CPU time limit increase to 5 minutes.
  • Updated documentation to specify new maximum CPU limit of 300,000 milliseconds.
  • Clarified the distinction between total time and CPU time for Workers.

Modified Files

  • src/content/docs/workers/wrangler/configuration.mdx

Added Files

  • src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

What is Hyperlint?

Hyperlint is an AI agent that helps you write, edit, and maintain your documentation.

Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation.

@mikenomitch mikenomitch force-pushed the mikenomitch/cpu-changelog branch from 510326d to 08fe2ab Compare March 24, 2025 22:27
@danlapid
Copy link
Contributor

Can we update https://developers.cloudflare.com/workers/platform/limits/#worker-limits to add a link showing the 30s http request are configurable?

@rita3ko rita3ko requested review from a team and GregBrimble as code owners March 25, 2025 13:21
Copy link
Contributor

@irvinebroque irvinebroque left a comment

Choose a reason for hiding this comment

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

Awesome. Can we call out wall time is unlimited because people get this mixed up often?


You can now run a Worker for up to 5 minutes of CPU time for each request.

Previously, each Workers request ran for a maximum of 30 seconds of CPU time. This
Copy link
Contributor

Choose a reason for hiding this comment

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

...while duration (wall-time) is unlimited in workers

(Or something)

@irvinebroque
Copy link
Contributor

Should this call out workflows and queues more loudly? Since these cover use cases for longer running tasks?

@rita3ko rita3ko merged commit bf77f14 into production Mar 25, 2025
11 checks passed
@rita3ko rita3ko deleted the mikenomitch/cpu-changelog branch March 25, 2025 15:31
RebeccaTamachiro pushed a commit that referenced this pull request Apr 21, 2025
* Adds changelog entry for cpu_ms limit bump

* update limits page

* Update src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx

Co-authored-by: Brendan Irvine-Broque <[email protected]>

* clarify wall clock vs cpu time

* mention workflows & queues

---------

Co-authored-by: Rita Kozlov <[email protected]>
Co-authored-by: Rita Kozlov <[email protected]>
Co-authored-by: Brendan Irvine-Broque <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:workers Related to Workers product size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants