High-Performance Order Storage (HPOS) – how to clean database
-
We’ve just migrated our test installation to High-Performance Order Storage (HPOS). So far so good. Everything works as it should. I can’t really say whether performance was improved. We will have to dive deeper into this. Metadata were copied from the postmeta table to woocommerce_order_itemmeta. That’s much better. However, since most of the data in the old postmeta table was created by Woocommerce orders we have now two tables with almost the exact same (enormous) size. This is far from perfect. Can we savely remove all order-related data from the postmeta table? Maybe, you’ve already created a bunch of queries for that task? This would make our life much easier. ??
HPOS is a good idea, but the implementation seems to be flawed. In a perfect world, you would provide a function for cleaning the database. Our database is now sized at a whopping 4.4 GB. This makes backups a nightmare.
While I really hope that HPOS will improve performance, the logic behind it is a bit unclear. Seems to me pretty much the same whether I run a query through the old postmeta table or a new one of almost the same size. Why would this be faster?
- You must be logged in to reply to this topic.
