bazelbuild/bazel

Add bazel flag for max_cas_entry size.

Open

#18,449 opened on May 19, 2023

View on GitHub
 (8 comments) (3 reactions) (1 assignee)Java (4,465 forks)batch import
P3help wantedteam-Performanceteam-Remote-Exectype: feature request

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

Description of the feature request:

As of today, the max_cas_entry_size is declared at the server side. In the event that Bazel sends a write request containing a digest larger than the specified max_cas_entry_size, the remote cache throws an 'out_of_range' error. By introducing a Bazel flag for max_cas_entry_size, it becomes possible to validate it on the client side, potentially eliminating the need for a round trip to the server. This improvement has the potential to enhance build performance.

What underlying problem are you trying to solve with this feature?

Improved build performance with remote cache.

Contributor guide

Research direction
Identify where the server side max cas entry size is enforced in the remote cache codebase. Understand how Bazel's client sends write requests to the remote cache. Then implement a client side flag that checks the digest size before sending the request, and update relevant tests.
Tech stack
java
Domain
build systemcli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaGitBazel Internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65