[נפתר] Performance issue resolved by WPML deactivate/reactivate - seeking root cause

Hello WPML Support Team,

I'd like to report a performance issue I recently experienced on a production WooCommerce store, which was resolved by deactivating and reactivating WPML. I'm hoping you can help me understand the root cause so I can prevent it from happening again.

**Site configuration:**
- WordPress with WooCommerce (recently updated from 10.5.3 to 10.7.0)
- WPML Multilingual CMS 4.9.2
- WPML String Translation 3.5.1
- WPML Multilingual & Multicurrency for WooCommerce 5.5.5
- WPML SEO 2.2.5
- PHP 8.2
- Shared hosting with a limit of 8 concurrent PHP processes

**What happened:**

The site became extremely slow - pages were taking 30+ seconds to load, and the hosting provider reported that the PHP process limit (8) was constantly being saturated. Processes would immediately respawn after being killed, indicating some kind of internal loop rather than external traffic pressure.

We ruled out the following as causes:
- Bots / external traffic (tested with IP whitelist blocking)
- Cache misconfiguration (WP Super Cache was not properly enabled - we fixed that, but the problem persisted)
- Action Scheduler queue (pausing action_scheduler_run_queue did help temporarily, but the issue returned)

We also completed a pending WooCommerce database migration (from DB version 10.5.3 to 10.7.0) which gave a brief improvement (page load dropped to ~2s), but the slowness returned shortly after.

**The fix:**

As a diagnostic test, I deactivated all WPML components. The site immediately became fast (under 2 seconds), though obviously translated content was unavailable. I then reactivated WPML, and to my surprise, the site remained fast.

**My questions:**

1. Do you recognize this pattern? Is there a known issue where WPML's internal state/cache gets into a bad state and requires reactivation to recover?

2. Could this be related to the WooCommerce database update that happened shortly before? Is there a known interaction where WPML for WooCommerce needs to be refreshed after a WC core database migration?

3. What's the recommended way to clear WPML's caches proactively? I see a "Clear Cache" option in WPML > Troubleshooting - is running this periodically a valid maintenance practice, or should it only be used for specific problems?

4. Are there any Performance settings you'd recommend reviewing for a WooCommerce site running on a hosting plan with limited concurrent PHP processes?

5. Is there anything in WPML logs or diagnostics I should check to understand what actually happened, so I can detect this state earlier next time?

The site is working fine now, so this isn't urgent - but I'd like to understand the cause to avoid repeating 3+ hours of troubleshooting next time. Any insight would be much appreciated.

Thank you,