elephone-184 opened a new issue, #4337:
URL: https://github.com/apache/rocketmq-dashboard/issues/4337

   ### Feature Description
   In RocketMQ storage architecture, reading messages from OS PageCache yields 
near-zero latency, whereas cold reads (falling behind into physical SSD/HDD 
CommitLog files) saturate disk I/O, causing severe broker write stalls and 
consumer slowdowns. Administrators need an inspector to monitor PageCache hit 
ratios, cold read throughput, and identify laggy consumer groups causing cold 
reads.
   
   ### Proposed Solution
   1. Introduce `BrokerColdReadReport` model tracking OS page cache hit 
percentage, cold read TPS, memory pressure index, and top cold-reading consumer 
groups.
   2. Implement `BrokerColdReadInspectorService` to calculate broker cold read 
ratios and memory working set metrics.
   3. Provide `BrokerColdReadInspectorController` with 
`/cluster/coldRead.query` endpoint.
   4. Add frontend `BrokerColdReadInspectorModal` with hit-rate progress bars, 
cold read group breakdown, and cache eviction warnings.
   5. Provide comprehensive controller and service unit tests.


-- 
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]

Reply via email to