Benjamin Peterson
Benjamin Peterson
Okay, it sounds like this is not workable as is. What do we think about a patch make a `memory.peak` writable by the transient unit's `User` and `Group`?
The usecase is an unprivileged tool that starts containers (with a memory limit) and wants to record to the peak memory usage of the containers it starts over various time...
It's configured by setting a property of the transient unit. E.g., `systemd-run --property MemoryMax=1G`.
You mean `MemoryPeak` would be made into a writeable unit property and processes that can mutate the unit can reset the peak threshold? It would work for me, though systemd...
https://github.com/bazelbuild/bazel/blob/114d7720ea52fbf613bc3e06dd746eb07ce5c335/src/main/java/com/google/devtools/build/lib/actions/ResourceManager.java#L63-L67 https://github.com/bazelbuild/bazel/blob/114d7720ea52fbf613bc3e06dd746eb07ce5c335/src/main/java/com/google/devtools/build/lib/actions/ResourceManager.java#L151-L158
> Side note: should we flip the default of `--experimental_stream_log_file_uploads` to true? Unfortunately, there's no public protocol for streaming uploads and consequently no implementation of this flag in Bazel.
@bazelbuild/triage Not stale
This issue still exists.
@bazelbuild/triage
This issue still exists.