Open Bug 1280641 Opened 4 years ago Updated 8 months ago

Implement a two-tier S3 cache for sccache

Categories

(Firefox Build System :: General, defect, P2)

defect

Tracking

(Not tracked)

People

(Reporter: ted, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: stale-bug, Whiteboard: [build-run-speed-up])

Currently sccache on try uses a different S3 bucket from inbound etc, because we don't want try builds to be able to poison the inbound cache with junk. Unfortunately this means that try builds don't benefit from cached objects that have already been built on other branches.

Once we fix bug 1280640 such that cross-branch cache hits are possible, we can add support to sccache for a two-tier S3 cache and configure try builds to use the inbound bucket as a read-only cache, and then still write to a separate bucket. This should make some try builds faster because they'll be able to pull objects from cache where they would have had to build.
Assignee: nobody → ted
Blocks: thunder-try
Whiteboard: [build-run-speed-up]
ted might be able to tackle this by the end of this month.
More info in dependent bug.
I also want to point out that it is unclear how much gain we will get from this work.
However, since it is not a lot of work to get it done as we will most likely get *some* gains even if not large.
P1 == we're commiting to complete this within this quarter.
Priority: -- → P1
Is this still being worked on?
Flags: needinfo?(armenzg)
ted: Is this still being worked on?
Flags: needinfo?(armenzg) → needinfo?(ted)
Not at present, but it's still something we'd like to have.
Flags: needinfo?(ted)
Priority: P1 → P2
Product: Core → Firefox Build System
Assignee: ted → nobody
You need to log in before you can comment on or make changes to this bug.