actions/upload-artifact
1
Fork 0
mirror of https://gitea.com/actions/upload-artifact.git synced 2024-11-26 02:25:58 +01:00
Code Activity

Update README.md

Browse source
This commit is contained in:
Konrad Pabjan 2021-01-07 18:56:21 +01:00 committed by GitHub
parent 16b8b2b2e7
commit a4f98af3fa
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -256,7 +256,11 @@ If file permissions and case sensitivity are required, you can `tar` all of your
name: my-artifact name: my-artifact
path: my_files.tar path: my_files.tar
``` ```
### Too many uploads resulting in 429 responses
A very minute subset of users who upload a very very large amount of artifacts in a short period of time may see their uploads throttled or fail because of `Request was blocked due to exceeding usage of resource 'DBCPU' in namespace` or `Unable to copy file to server StatusCode=TooManyRequests`.
To reduce the chance of this happening, you can reduce the number of HTTP calls made during artifact upload by zipping or archiving the contents of your artifact before an upload starts. As an example, imagine an artifact with 1000 files (each 10 Kb in size). Without any modification, there would be around 1000 HTTP calls made to upload the artifact. If you zip or archive the artifact beforehand, the number of HTTP calls can be dropped to single digit territory. Measures like this will significantly speed up your upload and prevent uploads from being throttled or in some cases fail.
## Additional Documentation ## Additional Documentation