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.
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.