This includes the ability to force using local images only (do not check
for updated manifests), and to explicitly mount and specify external caches
for Go repositories via `rules_go`'s `GO_REPOSITORY_USE_HOST_MODCACHE`.
PiperOrigin-RevId: 713473497
This is meant to be used as part of a pipeline to refresh the profiles used
for PGO builds. This is used to quantify how similar the profiles are to
existing checked-in profiles. If they are similar enough, then the checked-in
profiles do not need to be updated.
PiperOrigin-RevId: 700788407
This updates the Google Cloud APIs and their Go libraries to their latest
versions, which adds some of the missing fields of the container cluster
service v1 proto that didn't exist in the version defined in `WORKSPACE`.
This also severs the proto import dependency of `test_range_config.proto` on
the container cluster API proto, both because it shouldn't be GKE-specific
but also because the Go genproto version of the container cluster API is
different (from the Go linker's perspective) from the container cluster
proto that is imported from `test_range_config.proto`. Instead, it is
encoded as an "any" proto for both nodepools and clusters.
Go repositories are re-arranged such that the genproto version imported is
taken from the `WORKSPACE` file rather than the one embedded in other Go
repositories earlier in the file.
The version of this API in Go's genproto library is still missing some of
the TPU node placement fields, so that part is filled in via reflection
when available. That is hacky but that codepath only applies to TPU clusters
so not applicable for most benchmarks.
PiperOrigin-RevId: 688682505
This is a large set of Kubernetes-based performance benchmarks that has
been in use at Google for gVisor performance testing on GKE, and is now
open-source.
This set of benchmarks has been created and maintained by multiple
contributors over the last 2 years:
@zkoopmans, @EtiennePerot, @kevinGC, @ayushr2, @manninglucas,
@konstantin-s-bogom.
PiperOrigin-RevId: 686649688
The go_types_memoize.patch was generated using the git diff command, with
the 'go' field manually added to the path. It would be more appropriate to
set the patch_strip value to 1 when applying such patches.
Signed-off-by: Dawei Shen <shendawei.sdw@antgroup.com>
The key highlight from the release notes:
Build without the Bytes for builds using remote caching and/or remote
execution is now enabled by default (i.e. --remote_download_outputs
defaults to toplevel). This means that Bazel will no longer try to
download any intermediate outputs from the remote server, but only the
outputs of requested top-level targets instead. This significantly
improves build performance. Bazel now also handles the case of an
artifact falling out of the remote cache gracefully, by rewinding the
build.
Signed-off-by: Andrei Vagin <avagin@gmail.com>
This is part of a series of changes to add metric charts in performance
benchmarks.
This change adds the code to compile the metrics profiling data into charts,
rendering those charts to HTML, and writing this HTML file to a temporary
location.
It uses the Apache echarts library to generate the charts.
PiperOrigin-RevId: 631974672
Andrei Vagin
Etienne PerotandgVisor bot
Dawei Shen
Jing ChenandgVisor bot
Anthony CuiandgVisor bot
Anqi Shen
Andrei VaginandAndrei Vagin