The following functions have poor database performance:
The problem is that they restrict by taxonomy terms (one table) and sort by latest updates (another table). This will always result in temp tables and filesorts. The solution is unifying the WHERE criteria and SORT BY criteria into one table. In the case of forum_get_topics, the table is term_node. For forum_get_forums, it's term_data or term_hierarchy.
By putting a latest_change_timestamp (which would contain either the node's latest change timestamp or the latest comment's) into these tables, we can paginate forums without expensive queries. Once paginated, it's okay to do something a bit more expensive with each item.
Needs work
1.0
forum.module
It affects performance. It is often combined with the Needs profiling tag.
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Forum is approved for removal. See #1898812: [policy] Deprecate forum module for removal in Drupal 11 →
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.
It will be moved to the contributed extension → once the Drupal 11 branch is open.