Hello, my hosting provider's (Cloudways) slow-request log shows that "mark all read" requests are consuming very large amounts of PHP execution time. Multiple foro=allread URLs are averaging 15–22 seconds, with peaks of 30 seconds, each occupying a PHP-FPM worker for the full duration. On my server (2 vCPU), a few concurrent requests of this type saturate the worker pool and spike CPU.

This is a problem in two ways: automated crawlers hitting these URLs cause load spikes, but even a legitimate logged-in member clicking "mark all read" would wait 15–30 seconds for the action to complete. Please check this image https://ibb.co/0jpwdLnS

Could you advise:

1. What does foro=allread do internally that could take this long? Is it iterating over all topics across all forums per request?
2. Are there settings to limit its scope, or is this a known performance issue with a fix or workaround?
3. Is this improved in a newer wpForo version?

My environment, for reference: wpForo v3.1.2 , WordPress on Cloudways (NGINX/PHP-FPM Lightning stack), Elasticsearch via ElasticPress, Redis object cache, Cloudflare Enterprise in front.

Thank you — happy to provide logs, screenshots, or temporary access for either issue.

Warm regards,
Sarmad
paradigmshift.com.pk