Hello,
When a user hits reply the site takes over a minute (2/3 minutes) to reload the tab with the new post showing. If I browse the thread from another tab, the reply is visible much faster. Any ideas? I added some monitoring, it seems the SQL is taking a while to load. Posts table is confirmed InnoDB.
@gianttoe,
Replying in wpForo can take a long time to reload the topic with the new post showing due to performance issues related to the insertion and update process of new posts. Even if your posts table is InnoDB, slow queries during posting can cause delays. This is a known issue where reading forum pages is fast, but publishing or replying can be slow, sometimes taking 10-30 seconds or more. The delay is often caused by heavy database operations and possibly email sending processes triggered on posting. Caching does not speed up posting because it involves database writes and other backend processes.
To improve performance, consider these points:
- Check for slow queries related to wpForo using tools like Query Monitor.
- Disable any cache plugins for wpForo, as caching does not help posting speed and can cause conflicts.
- Review and possibly disable email notifications temporarily to see if that speeds up posting.
- Ensure your hosting environment has sufficient CPU and memory resources, as posting is more resource-intensive than browsing.
This behavior has been discussed in the wpForo support forums where users report fast page loads but slow posting times, sometimes related to server resources or database query optimization. Unfortunately, large topics with many replies can also contribute to slower post insertions.
If you want to dig deeper, monitoring slow queries and debugging wpForo's post insertion process is recommended.
Hello,
When a user hits reply the site takes over a minute (2/3 minutes) to reload the tab with the new post showing. If I browse the thread from another tab, the reply is visible much faster. Any ideas? I added some monitoring, it seems the SQL is taking a while to load. Posts table is confirmed InnoDB.
This is a common issue when your forum starts to get big mate. Its the email queue. Everyone on a particular thread needs to be emailed and notified of replies and things like that, so the bigger the thread, the more people need to be sent notifications. You need to set up an email queue, I use this one:
Get that up and running, its reasonably easy, and you should see the timing reduce a lot. Still takes a few seconds, but no where near as long as it does without it.
Hey, sounds like the page reload is getting hung up somewhere on the database side. Since the reply shows up quickly when you open the thread in another tab, it’s probably not the post itself that’s slow to save, but rather the page refresh after you hit “reply.” That usually means the query or process that runs after posting — like updating counts, notifications, or reloading all replies — is taking longer than it should. If your monitoring shows the SQL load spiking, it’s likely the query fetching or updating posts is slow or stuck waiting on something. In some cases, this happens because the posts table or related tables are under heavy locking or missing the right indexes, so even though the post saves fine, the page waits until everything finishes before it reloads. You might also be seeing delays if background tasks like email or webhook notifications are processed during that reload instead of running asynchronously. It’s one of those issues where everything technically works, but it feels sluggish because the database or app is doing too much right after a reply is posted.
I'll leave my answer here.
The problem was not the forum, the indexes were not built/present. Ask AI to build a monitoring tool to its own log on the server so its not polluted by other stuff. As for all activites and timings. Hit reply, get the log, feed it to AI and get the indexes required and apply them to the SQL database.
