Skip to content

Commit 06f2adc

Browse files
Update src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
Co-authored-by: Brendan Irvine-Broque <[email protected]>
1 parent 5a18847 commit 06f2adc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ You can now run a Worker for up to 5 minutes of CPU time for each request.
1212

1313
Previously, each Workers request ran for a maximum of 30 seconds of CPU time. This
1414
meant that some compute-intensive tasks were impossible to do with a Worker. For instance,
15-
a user might want to take the cryptographic hash of a large file from R2. If
15+
you might want to take the cryptographic hash of a large file from R2. If
1616
this computation ran for over 30 seconds, the Worker request would have timed out.
1717

1818
By default, Workers are still limited to 30 seconds of CPU time. This protects developers

0 commit comments

Comments
 (0)