You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/08/11 07:26:57 UTC

[I] [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview [rocketmq-dashboard]

Aias00 opened a new issue, #1660:
URL: https://github.com/apache/rocketmq-dashboard/issues/1660

   ## Problem
   
   `RocketMQDashboardProvider.collectDashboardData()` calls `examineTopicRouteInfo(topic)` once for every non-system Topic solely to derive per-cluster topic counts. Large clusters turn one overview refresh into hundreds or thousands of sequential NameServer route requests.
   
   ## Why this needs a design decision
   
   A Topic can span brokers and cluster ownership is not represented in the topic list. Skipping route lookup without a replacement would make per-cluster counts incorrect.
   
   ## Proposed direction
   
   - Evaluate a bounded/cached route-resolution strategy with an explicit freshness policy, or a backend aggregate endpoint.
   - Make any partial result visible to the UI rather than reporting it as a complete count.
   - Add a large-topic-count benchmark and ensure refresh latency/RPC volume remain bounded.
   
   ## Track
   
   Track 1 / dashboard runtime observability.


-- 
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: commits-unsubscribe@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview [rocketmq-dashboard]

Posted by "Aias00 (via GitHub)" <gi...@apache.org>.
Aias00 commented on issue #1660:
URL: https://github.com/apache/rocketmq-dashboard/issues/1660#issuecomment-5250528008

   Re-verified against current `rocketmq-studio` baseline (`9371e2a0`). The reported `RocketMQDashboardProvider.collectDashboardData()` implementation and its per-Topic `examineTopicRouteInfo` loop are no longer present in the source tree; the current dashboard path uses `DashboardProviderStub`.
   
   The issue was discovered from an older worktree/revision and is not reproducible on the current baseline. Closing to avoid tracking a stale performance regression. A future live dashboard provider should include an explicit bounded aggregation/freshness design before introducing route-derived cluster counts.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview [rocketmq-dashboard]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #1660:
URL: https://github.com/apache/rocketmq-dashboard/issues/1660#issuecomment-5363576396

   This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview [rocketmq-dashboard]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #1660: [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview
URL: https://github.com/apache/rocketmq-dashboard/issues/1660


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview [rocketmq-dashboard]

Posted by "Aias00 (via GitHub)" <gi...@apache.org>.
Aias00 closed issue #1660: [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview
URL: https://github.com/apache/rocketmq-dashboard/issues/1660


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Studio][Performance] Avoid per-Topic route RPCs in Dashboard cluster overview [rocketmq-dashboard]

Posted by "Aias00 (via GitHub)" <gi...@apache.org>.
Aias00 commented on issue #1660:
URL: https://github.com/apache/rocketmq-dashboard/issues/1660#issuecomment-5250683189

   Correction after revalidating the latest `rocketmq-studio` baseline (`65d1c328`): `RocketMQDashboardProvider.collectDashboardData()` is present and still calls `examineTopicRouteInfo(topic)` once per non-system Topic. My prior closure was based on an outdated local checkout that lacked this provider.
   
   Reopening the issue. I will proceed with a bounded strategy and preserve explicit partial-result semantics rather than silently reporting incomplete per-cluster counts.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org