x/build/cmd/coordinator: mind combined memory usage when concurrently processing large payloads #51057
Labels
Builders
x/build issues (builders, bots, dashboards)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Milestone
As part of WriteTgz/PutTar operations, the coordinator handles payloads that may be large (for example, a Go tree tarball is 23 MB, and the x/website tree is even larger). If the entire payload size is read into memory during the processing of these operations, then multiple operations made in parallel can lead to coordinator using up much more memory than it does under a more average workload, and exceeding its current 8 GB memory limit.
For now, we can double that limit to give it more room to handle workloads that may happen as part of normal Go development and debugging, without getting killed due to OOM.
Keeping this issue open to see what else we may need to do. There are various opportunities to investigate and consider:
CC @golang/release, @thanm, @aclements.
The text was updated successfully, but these errors were encountered: