magento / magento/community-features
Parallelization of the catalog:image:resize process
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
As of Magento 2.2.6 the catalog:image:resize process is really slow : It can take approximately 12 hours to process a 130000 items catalog using high end hardware. The issue seems to be amplified by themes that make uses of image types (eg. Porto).
Resource wise, the process uses 1 core and low IO.
The nature of the task lends itself quite well to paralellisation and I believe it would be rather simple to implement since there is probably some boilerplate code available in the indexers.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the catalog:image:resize process and comparing its structure with the existing indexers, which the issue identifies as a possible source of parallelization boilerplate. Define completion by demonstrating parallel processing and improved throughput on a large catalog while preserving image-resize behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100