Large performance impact when `ACTIONS_STEP_DEBUG` is enabled
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
There is a large performance impact when ACTIONS_STEP_DEBUG is enabled. I have a test repo here https://github.com/billyvg/test-actions-cache/runs/3236458097?check_suite_focus=true that compares actions/cache@v1 vs actions/cache@v2 with logging enabled vs disabled. The results (with a sample size of 1 here) are as follows for a cache size of roughly 180MB.
| - | no logging | w/ logging |
|---|---|---|
| v1 | 24s | 31s |
| v2 | 8s | 35s |
Ideally, we'd want to always have ACTIONS_STEP_DEBUG enabled, so it'd be nice to have the option of completely suppressing the logging from actions/cache.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked test-actions-cache run and compare actions/cache@v1 and @v2 under ACTIONS_STEP_DEBUG enabled and disabled. Trace where cache logging is emitted, then define how logging could be completely suppressed and verify the change against comparable cache-size performance measurements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100