HPOS cleaning post/postmeta data

  • Resolved Colissimo

    (@iscpcolissimo)


    1 year, 4 months ago

    Hello,

    Will you be adding an option to clean the post and postmeta tables from WooCommerce data once the HPOS option is stable?

    We have over 2.5M postmeta entries related to WooCommerce order/subscriptions/addresses that slow down a lot our website. The main purpose of the HPOS feature is to avoid that, but if there is no way to clean the data once the sync is done, it doesn’t help much.

    If you don’t intend to add an option to clean the wc data from the post/postmeta tables, could you tell me if it’s safe to run DELETE queries on these tables for shop_order/shop_subscription posts?

    Thank you

Viewing 15 replies - 16 through 30 (of 45 total)

  • @catvetbeb first of all you do not know the ammount of work that goes into developing a plugin, secondly you can wait and buit them on sales (with high discounts), thirdly this is going offtopic.

    Thread Starter Colissimo

    (@iscpcolissimo)

    Guys can you please stop arguing on my thread? I’d like it to stay relevant in case the WooCommerce team adds useful information to it.

    I would also like to clean the post and postmeta tables from WooCommerce data once the HPOS option is stable.

    save for updates about this topic

    After upgrading to HPOS, our DB grew extremely in GB’s. We definitely need an option to clean the old legacy entries. I hope the WooCommerce team will make a priority of this, since this is slowing down our site significantly.

    @jzn21 it is normal, since you most probabbly have it set up in compatibility mode where it duplicates the current order data (old) into new tables (new) thus needing 2x more space for each order + history, it should not be a concern as long as the copy is not used (for now) but if you use only the new method, then yes! As postmeta is linked to all posts in a WP setup.

    Plugin Support Feten L. a11n

    (@fetenlakhal)

    Hi there!

    Thanks for contacting us here at WooCommerce.com!

    We don’t think that such a feature would be added. WooCommerce won’t be querying that data so we wouldn’t expect any negative impact by leaving the existing data intact.

    Can you please explain how it slows down your website? What is querying the data??

    Just for storage and space saving purposes. Can we simply drop those old tables if we’re using only HPOS ? Or is there other data in those tables that’s still used for WordPress?

    @fetenlakhal yes but for existing stores it is a performance impact on other site areas, this is not OK! Why should blog posts / pages be impacted by data that is not used (anymore) by WooCommerce?

    @korvak the _postmeta and _posts table are used globally by all posts in WordPress; that’s why we need a function implemented and teste by WooCommerce, it’s not a simple “empty table click / query”

    WOW ! Thank you wordpress ! After waiting more than 10 years for your to figure out how to improve your database, we will now have to wait 10 more years for you to finally understand how idiot it is not to propose a way to clean the database !?! Is there anybody smart in this company ?!?!?!

    Anyone interested, the WooCommerce team will make this happen.

    See https://github.com/woocommerce/woocommerce/issues/41062

    Thread Starter Colissimo

    (@iscpcolissimo)

    Hello @fetenlakhal,

    As @rwky explained, WooCommerce isn’t the only one that queries the _postmeta table: the core post/page system uses it, as well as every plugin based on posts to create content (event plugins if you really need an example). These are slowed down quite a bit the more this table has data.

    If you do add a way to clean the data like @mondalaci said, please do NOT overlook the WooCommerce Subscriptions data added in the _postmeta table which is huge.

    Have a nice day

    Plugin Support abwaita a11n

    (@abwaita)

    Thanks for your input!
    For anyone else landing on this thread, I’d recommend starting by checking out the enhancement request here, which has more information and feedback from our developers – https://github.com/woocommerce/woocommerce/issues/41062.

    Feel free to share any other thoughts there so our developers can take them into consideration.

    I came here to look for help with this and nothing has been resolved yet?

    @nossileee there is a response above you where it explains why this is very complicated for existing installs, it will take a while, sadly.

Viewing 15 replies - 16 through 30 (of 45 total)
  • You must be logged in to reply to this topic.

Tags