Repository navigation
Feature Request: Configurable UI Refresh Rate / API Polling Interval #1681
Replies: 1 comment
Agent BriefCategory: enhancement Current behavior: Desired behavior:
Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Scope is a maintainer call: whether the knob is global or per instance, what minimum is safe to offer given that a short interval multiplies |
Uh oh!
There was an error while loading. Please reload this page.
Currently, the UI updates feel a bit slow because the refresh rate / API polling interval seems to be hardcoded. While I completely understand that a conservative polling rate is necessary for performance when managing massive setups with tens of thousands of torrents across multiple instances, it makes the UI feel less responsive and "laggy" for users with smaller or medium-sized setups.
Describe the solution you'd like
It would be great to have a configurable refresh rate. Ideally, a dropdown in the Web UI settings (or a parameter in config.toml) where users can select their preferred polling interval based on what their backend can handle (e.g., 1s, 2s, 5s, 10s, Default).
Describe alternatives you've considered
I've looked through the config.toml and the UI settings hoping to find a hidden setting to increase the update frequency, but couldn't find any existing way to adjust this.
Additional context
Allowing users to opt-in to a faster refresh rate would make qui feel much snappier and provide better visual feedback for those of us whose servers can easily handle more frequent API calls to qBittorrent.
All reactions