Image Optimization - Create new ImagePool for each batch #470
No reviewers
Labels
No Label
a11y
Backlog
Blocked
Bug
Content
Dependencies
Design
Feature Request
Good First Issue
In Progress
Performance
Priority - High
Priority - Low
Priority - Medium
Untriaged
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: www/www-new#470
Loading…
Reference in New Issue
No description provided.
Delete Branch "amy-image-optimization-image-pool"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have been having issues with the image optimization script consuming egregious amounts of memory and failing CI as a result. Previously, we tried processing images in "batches" in order to reduce memory usage, however this fix did not work for long.
This PR changes the script so that we use a new
ImagePool
to process each batch of images. Preliminary results in my local environment and on CI seem promising, and this is a relatively low risk (and low effort) change, so let's see how it holds up.