• Resolved Mortn

    (@hedloff)


    Hello,

    We manage several Woocommerce sites that are different in sizes.
    Many backup plugins has issues dumping database because of _postmeta and _woocommerce_order_itemmeta is to big and taking to long.
    For example we have one site that has _postmeta table with 4.000.000 rows and 540MB in size.
    And _woocommerce_order_itemmeta on same site is 2.020.000 row and 2.9GB in size.

    Is it possible to split all Woocommerce db queries into a seperate database somehow?
    Or split the tables somehow?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hey @hedloff,

    Is it possible to split all Woocommerce db queries into a seperate database somehow?
    Or split the tables somehow?

    I am not aware of any extensions that would help you split the tables. It may be possible but would require a significant amount of custom development work.

    If you’re struggling with performance issues due to the size of the tables then there are articles online that outline ways you can optimize and clean up the database to reduce the size.

    If the primary issue is creating backups of the database due to the size then you may need direct access to your database so that you can generate backups directly on the server.

    To then reimport the database you may need to look for a tool that will split the mysql dump into smaller files so that you can re-import.

    I hope that helps!

    Kind regards,

    Thread Starter Mortn

    (@hedloff)

    No issues with performance yet. The issue is your plugin filling _postmeta table.
    I don’t think we should remove those as that will remove previous orders from customers?

    No issue with creating backup either, but as your plugin is filling tables it will takes hours to backup the database.

    That’s why I was looking for a solution, but I guess Woocommerce cannot handle huge ecommerce sites, so we will need to look for alternatives.

    Plugin Support Niall a11n

    (@wpniall)

    Hi @hedloff,

    Thanks for your feedback and for sharing your issues with the _postmeta table.

    If you’re concerned about whether WooCommerce can handle large eCommerce sites or not, I highly recommend having a look at this doc, which explains how WooCommerce can handle them: WooCommerce Scaling FAQs.

    As your post involves a fairly complex development topic, I’m going to leave it open for a bit to see if anyone is able to chime in and help you out.

    I highly recommend joining the #developers channel of the WooCommerce Community Slack and maybe the WooCommerce Facebook group. We’re lucky to have a great community of open-source developers for WooCommerce, and many of our developers hang out there too. I think somewhere there might be able to provide more detailed insight into the problem you’re having.

    Thank you!

    Mirko P.

    (@rainfallnixfig)

    Hi there,

    It’s been a while since we last heard back from you. I’m going to mark this thread as resolved.

    Hopefully, the above information was helpful. If you have further questions, please feel free to open a new topic.

    Cheers.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Huge postmeta table and woocommerce_order_itemmeta’ is closed to new replies.