Test Performance of "large" build artifact uploads

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Topic to Evaluate

How big is too big of a build artifact to upload? As a follow-up to #221263 we want to evaluate how changing the limit of artifact uploads would impact performance and system stability.

At a minimum we should test 1, 2, 5 and 10gb file sizes to capture current performance and how changing the limit would impact that. Testing different file types / object storage methods could also be of interest.

@shampton @cheryl.li could you fill in some technical bits here of what to evaluate (time to upload, runner performance, ??)

  • Link to other Issue

Tasks prior to evaluation

#322817 (closed) should be finished.

  • Clearly document the topic to evaluated in this issue description
  • Determine specific scope including time-bounds for investigation

Tasks to Evaluate

  • Determine feasibility of the feature
  • Create issue for implementation or update existing implementation issue description with implementation proposal
  • Set weight on implementation issue
  • If weight is greater than 5, break issue into smaller issues
  • Add task
  • Add task

Risks and Implementation Considerations

Team

  • Add workflowplanning breakdown typefeature and the corresponding ~devops::<stage> and ~group::<group> labels.
  • Ping the PM and EM.
Edited Aug 19, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading