links

hardware

loading

this pc

waiting for a read

pc data flowwaiting for a readno feed yet

no feed yet

solid: read · dashed: no read

data paths

loading specs

read / write / total · % of link max · pick a path for rates

hardware data pathscpu and gpu caches, memory, host links and io paths. loading specs.loading map

<50% 50–80% ≥80% · no read = unknown

gpu stats

no feed

no read

active time ≠ byte flow

pick a path

record

up to 300 fresh reads, kept in this tab. save before reload or close.

stopped · 0 reads

pick a path to plot.

saved readsno saved readsno saved reads
all rates
path / wayread ratespec limitsource / sample
loading specs
what the reads mean
maplogical paths, not exact board lanes. arrows show direction; motion is not speed. pick a line or table row for its source.
ageupdates about every 10s. reads older than 45s are stale; motion stops.
disk and netreal bytes per sec; all apps count. host io is a shared path in this map, not a measured chip.
gpu linknvidia's coarse MB/s reads. a zero may hide small flows. the rates are for the host link.
ram and useram and cache flow are not measured. part bars show busy time or space used, not byte flow.
limitsdated specs and labeled scenarios, not live speed tests. each path keeps its own scope and source.
flow barsread/write use the host or core view. total adds both reads; its max adds both ways for full duplex, or uses one shared max. bars compare host bytes with link limits, before packet overhead. drive ratings stay in the specs. colors show load, not health.
unitsB/s is bytes per sec. GB/s uses 1,000,000,000 bytes.
recordup to 300 fresh, unique reads in this tab. no server history. save the csv before reload or close.
gapsno read = data is missing. no values are made up.