Good day. Our site has become unusable when ATUM and MI are active. Specifically MI. It's consuming huge PHP resources and this hasnt' happened before. Not sure if it's linked to WC updates or what. Basically site freezes up and end up timing out. We have a lot of items in MI so it's not ideal - please advise.
What I’m seeing:
I’ve put 3 tables in your workspace:
Top 20 query/resource patterns by total time
Share of total time (ATUM vs Other)
Top ATUM-related query patterns
From this export:
≈65% of total query time is ATUM/Multi-Inventory related.
(Joins against wp_atum_product_data etc. dominate.)
The single biggest pattern by total time is a query like:
SELECT p.ID FROM wp_posts … LEFT JOIN wp_atum_product_data apd … (apd.price_per_inventory …)
That’s MI logic crossing posts ↔ atum tables (price-per-inventory/availability checks).
Next heaviest buckets are wp_options reads/updates (lots of calls to alloptions and autoload loads). Frequency is high; each is cheap, but the total adds up—this is where object cache (Redis) helps most.
What to do now (targeted):
ATUM MI tuning (biggest win)
If you don’t need MI detail on shop/category archives, turn that off; keep full MI only on single product pages.
Prefer priority inventory selection over dynamic per-inventory price checks if possible (that price_per_inventory join is expensive).
Trim the number of inventories per product where you ca
