-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache task is slow and unreliable #10935
Comments
Thanks for reporting! The moment of your cache retrieval coincided with load on that scale unit quadrupling in load. Our automatic scaleout trigger, but had some lag. We'll see what tweaks we can make to make this better. Can you confirm you are not seeing this consistently? |
Possibly the same as #10917 |
I haven't seen the Serve Unavailable error anymore. The performance seems to vary a bit. From what I gather you are currently uploading files separately? If so uploading a tarball with fast compression might help a lot when you have lots of small files. |
👍 #10925 |
Yes, I think so. If I hit this again we can always revisit. |
Fallback keys: microsoft/azure-pipelines-tasks#10842 input globbing: microsoft/azure-pipelines-tasks#10859 Relative paths: microsoft/azure-pipelines-tasks#10858 Only save when restore runs: microsoft/azure-pipelines-tasks#10907 Retries on timeouts: microsoft/azure-pipelines-tasks#10935
* New features for Pipline Cachings: Fallback keys: microsoft/azure-pipelines-tasks#10842 input globbing: microsoft/azure-pipelines-tasks#10859 Relative paths: microsoft/azure-pipelines-tasks#10858 Only save when restore runs: microsoft/azure-pipelines-tasks#10907 Retries on timeouts: microsoft/azure-pipelines-tasks#10935 * Some PR feedback
For me, - task: NodeTool@0
inputs:
versionSpec: '16.x'
displayName: 'Install Node.js'
- script: yarn
displayName: Yarn install
- script: yarn lint
displayName: Run linting And with Cache takes variables:
YARN_CACHE_FOLDER: $(Pipeline.Workspace)/.yarn
# ....
- task: NodeTool@0
inputs:
versionSpec: '16.x'
displayName: 'Install Node.js'
- task: Cache@2
inputs:
key: 'yarn | "$(Agent.OS)" | yarn.lock'
restoreKeys: |
yarn | "$(Agent.OS)"
yarn
path: $(YARN_CACHE_FOLDER)
displayName: Cache Yarn packages
- script: yarn
displayName: Yarn install
- script: yarn lint
displayName: Run linting I followed the cache documentation. Am I doing something wrong? |
The caching Task often seems to pause for no reason at all. This happens on multiple agents... |
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: CacheBeta@0
Environment
Issue Description
The cache unfortunately appears to be slow and unreliable. I just tried it with a project that uses a fair bit of node_modules. On the first test:
[error]One or more errors occurred. (Service Unavailable) (Service Unavailable)
after downloading 359Mb of of 497Mb (72%)On a second test:
Which means the overall build time is still 16 seconds longer than without a cache.
Task logs
The text was updated successfully, but these errors were encountered: