mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Would it be more reasonable to sort this list by default from low to high for [Average upstream response time]? #5897
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#5897
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @devnakx on GitHub (Feb 4, 2026).
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
The problem
As shown in the figure, this list is currently sorted by default from highest to lowest

Proposed solution
But I believe that when it comes to response time, the lower the better

Therefore, it would be most reasonable to sort them from low to high by default
Alternatives considered and additional information
No response
@tjharman commented on GitHub (Feb 4, 2026):
In my mind you sort them highest to lowest so you can see those that aren't performing well and potentially remove them from service.
The fact you can change the sort order already lets you do what you want, but I do understand you're asking for it as default.