Magento 2.4.5 on 4GB RAM 2 CORE CLOUD SERVER


When running this command bin/magento catalog:images:resize

it has taken 2 days which is 48 hours to complete 50% so another 2 days are needed to complete the task. 4 days ! it is showing 56826 images

is this correct behaviour? Is there any way to make this process faster? there is 4GB on server and we have dedicated all of it Magento - disabled elasticsearch and crons. but it doesnt make any difference - the command is not using up max available RAM

  • It depends how many product you have, if it is in billions it will take long time. Another way is you can use reindex command. Commented Nov 29, 2022 at 11:43
  • there are 35000 products - please explain more about the reindex command how does this help and how can it be used for this task
    – nem3943
    Commented Nov 29, 2022 at 11:46
  • Just you need to run php bin/magento index:reindex command and check. Let me know is it helpful. Commented Nov 29, 2022 at 11:54
  • how does running that help with image resize? not making sense 2 commands do different things
    – nem3943
    Commented Nov 29, 2022 at 12:01
  • images resize is one aspect of storage requirements. reindex assists in making queries complete in less time (and helps reduce resource requirements). With a 4G and 2 Core server, performance may be disappointing, depending on results of @@max_used_connections; - which is max used concurrent connections since instance was started. If this is more than 20, consider a system with more RAM and Cores. Commented Dec 10, 2022 at 2:08

2 Answers 2


try to use this command with async flag. Example

bin/magento catalog:images:resize --async

ref: https://experienceleague.adobe.com/en/docs/commerce-operations/implementation-playbook/best-practices/development/catalog-image-resizing

Or or a terribly banal way but it works! Just open 5-10 terminal sessions and run a command on the instance in each of them. Multithread :))


Old thread! But another option for this is to stop using the application catalog:images:resize logic all together, and opt for edge resizing (nginx, CDN etc)


Main perks to edge resizing are

  • Significantly Less Disk Usage (seen reductions of a few hundred gig!)
  • No long bulk processes to handle resizing

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.