DRAM must refresh or it loses data. Refresh steals bandwidth. Scheduler policy determines how much.
Distinguish tREFI (average refresh-command interval), the full refresh window and tRFC (refresh recovery time).
Distinguish a row hit, an idle-bank access and a row conflict from the command sequence each requires.
Measure useful bytes per interval; account for overlapping scheduling, refresh and turnaround effects without double-counting.
Applies bandwidth budgeting specifically to DRAM scheduler behavior.
No. Counters can overlap or describe different boundaries. Reconcile them with actual service and useful bytes.