• Resolved Jose

    (@giuse)


    Hello,

    the memory usage of WooCommerce is dramatically high, and it becomes bigger and bigger with every new version.
    Are the authors doing something to have it under control?

    Here just two smoke tests:

    https://plugintests.com/plugins/wporg/woocommerce/latest

    https://plugintests.com/plugins/wporg/woocommerce/7.2.0

    Have a look at the table Benchmark.

    The last version 9.1.4 without any other plugin consumes 13.3 Mb of memory on the page /wp-admin/post-new.php?post_type=page.
    It consumes 7.4 Mb on the front page.
    Old versions like v. 7.2.0 were already heavy, but now the performance is becoming a disaster.
    On one of my computers, I cannot install WooCommerce because the CPU has insufficient power.

    Do you know about this serious issue? Usually, WooCommerce is installed with other heavy add-ons.
    This means if you want an e-commerce powered by WooCommerce and you want to log in to the backend, you need a very expensive server.
    The plugin was never very light, but now we have exceeded the acceptable limits. It’s really becoming ridiculous. 13.3 Mb of memory usage? Are we joking?
    Is there something that you can do to optimize the plugin and consume less memory?
    Why do you call all sorts of stuff everywhere? Is it possible to make the plugin more modular?

    Thank you.

Viewing 1 replies (of 1 total)
  • Stef

    (@serafinnyc)

    Hello @giuse yours is more of a statement than a support question. Although, I’m not sure why your computer won’t allow you to install it. CPU shouldn’t be affected unless you’re running multiple applications on your device. Have you installed WordPress? That’s even bigger. Try closing other applications on your computer.

    I would also suggest heading over to Git and share your thoughts there. This is the Git link and you can share your ideas with the team there. You can also put in feature requests, help code and all those fun things, etc.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.