RockteMQ-AI commented on issue #3167: URL: https://github.com/apache/rocketmq-dashboard/issues/3167#issuecomment-5545262518
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** `RocketMQDLQProvider.listDLQGroups()` (backend), DLQ search component (frontend) **Compatibility:** No breaking changes — internal performance improvement. This is a well-identified performance issue. The two problems are independent and both worth fixing: 1. **Serial `examineTopicStats` calls** — With a page size of 20, the current code waits for 20 sequential admin RPCs. Bounding parallelism (e.g., `CompletableFuture` with a semaphore of 4–8) would cut wall-clock latency significantly while keeping deterministic ordering by collecting results into the original slot order. 2. **Keystroke-triggered scans** — The search input fires a full backend scan on every character. Adding a debounce (300–500ms) on the input state change — while keeping the initial load and explicit search-submit immediate — would eliminate redundant scans without affecting UX. Both changes are localized and low-risk. A single topic-stats failure isolating to `UNAVAILABLE` for that row (while returning the rest) is also good defensive behavior. --- *Automated evaluation by @RockteMQ-AI* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
