# Disabled plugins still causing performance impact

**URL:** https://meta.discourse.org/t/disabled-plugins-still-causing-performance-impact/386419
**Category:** Bug
**Tags:** pr-welcome
**Created:** [October 22, 2025, 10:00am UTC](https://meta.discourse.org/t/disabled-plugins-still-causing-performance-impact/386419 "2025-10-22T10:00:15Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [October 22, 2025, 10:00am UTC](https://meta.discourse.org/t/disabled-plugins-still-causing-performance-impact/386419/1 "2025-10-22T10:00:15Z")

</div>

Since a lot of plugins have been bundled with core, we’ve been seeing some performance impact.

When investigating, it turned out that **some plugins are still injecting certain queries, even when disabled**.

An example is the topic voting plugin.

The [topic filter](https://github.com/discourse/discourse/blob/main/plugins/discourse-topic-voting/plugin.rb#L48-L78) and the [search filter and search order](https://github.com/discourse/discourse/blob/main/plugins/discourse-topic-voting/plugin.rb#L105-L116) are _always_ injected and active.

The code should be fenced with `SiteSetting.topic_voting_enabled`. Or maybe calls like `register_search_advanced_filter` should behave more like `add_to_serializer` and check if the plugin is enabled.

---

_[View the full topic](https://meta.discourse.org/t/disabled-plugins-still-causing-performance-impact/386419)._