8000 Cache gets slower over time · Issue #487 · actions/setup-java · GitHub
[go: up one dir, main page]

Skip to content

Cache gets slower over time #487

@Dogacel

Description

@Dogacel

Description:

The cached build gets slower over time.

Task version:
v3.11.0

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Repro steps:

  1. Create a scala, sbt project with build workflow.
  2. Cache target/ directory between runs to run sbt compile incrementally in consequtive commits in a PR.
  3. Wait a couple days and re-try.

Expected behavior:

Because we don't have any snapshot dependencies, cache sped should be preserved.

Actual behavior:
Whenever our sbt cache gets older, probability of it running slower increases.

I have realized no console log is given during this time, meaning no actual compilation happens but something

This is the average runtime for our workflow runs over time.

image

Sometimes the average goes down because sbt cache is refreshed. The average goes down slower as the existing PRs that use the old cache is closed.

I suspect might be related to #408 as sbt relies on both JDK / JRE hashes and dependency hashes.

In our case, the incremental build goes from 2m to 8m slowly. And it never exceeds 8 minutes. I also measured sbt update time which is around 6 minutes. I suspect update is happening even though the cache is there.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0