Skip to content

Restore ROCm job for Ubuntu - #27399

Merged
ggerganov merged 4 commits into
ggml-org:masterfrom
superm1:master
Aug 22, 2026
Merged

Restore ROCm job for Ubuntu#27399
ggerganov merged 4 commits into
ggml-org:masterfrom
superm1:master

Conversation

@superm1

@superm1 superm1 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Overview

Restore the Ubuntu 22 ROCm job with a working ccache.

Additional information

ccache stopped working for two reasons:

  1. We enabled more architectures and were living on the edge and blowing the size away and thus only had 500MB of cache hits.
  2. ccache on mtime doesn't work with ROCm delivered from pip wheels (there is a new mtime on clang for each build). We need to change it to content.

Requirements

Used to do experiments and identify the root cause.

@superm1
superm1 requested a review from a team as a code owner August 19, 2026 16:14
@superm1

superm1 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

CC @jimw567
CC @CISC
CC @IMbackK

@github-actions github-actions Bot added the devops improvements to build systems and github actions label Aug 19, 2026
Comment thread .github/workflows/release.yml Outdated
Comment thread .github/workflows/release.yml Outdated
@ggerganov

Copy link
Copy Markdown
Member

2GB of the cache seems like a lot for this job - this is 20% of our total budget (10GB). Btw, how long does the build take now?

Anyway, I think we have to start migrating our linux CI to HF-hosted infrastructure. We are starting to hit some hard limits here.

@jimw567

jimw567 commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

2GB of the cache seems like a lot for this job - this is 20% of our total budget (10GB). Btw, how long does the build take now?

Anyway, I think we have to start migrating our linux CI to HF-hosted infrastructure. We are starting to hit some hard limits here.

Here is the data from mtime and content based warm runs on the default github runner (4 vCPUs). As shown in the table the ccache is 431MB. We could live with 1GB, I guess. I am also setting up some runners with more CPU cores to speed up cold run as well. As a reference, my regular machine has 16 cores and the build takes about 30mins.

image

@CISC

CISC commented Aug 20, 2026

Copy link
Copy Markdown
Member

The main issue was probably mtime, upping the size to 1G should be more than enough and will likely never be fully used.

@ggerganov

Copy link
Copy Markdown
Member

Ok, let's change to 1 GB and we can look to merge. Though we should likely wait for the Release CI to flush a bit - we can probably give it a try over the weekend.

@CISC CISC added the merge ready A maintainer can use this label to indicate that they consider the changes final and ready to merge. label Aug 21, 2026
superm1 and others added 3 commits August 22, 2026 00:03
The ROCm toolchain is pip-installed fresh on every run, so the clang binary's
mtime changes each time. With ccache's default compiler_check=mtime that
invalidates the whole cache and warm builds only reached ~70% hits. Hash the
compiler contents instead so the cache survives toolchain reinstalls.
We're waivering with so many architectures built, we need a bigger
ccache limit.
@ggerganov
ggerganov merged commit e85caa8 into ggml-org:master Aug 22, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devops improvements to build systems and github actions merge ready A maintainer can use this label to indicate that they consider the changes final and ready to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants