Linux / resource measurement scope · Primary-source explanation; no UK IPTV implementation or account test. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Identify what the graph totals
GNOME System Monitor provides recent network-resource information alongside processor and memory observations. Before using a rate in a playback report, identify the interface and whether the display aggregates traffic. A whole-system graph does not inherently separate a television programme from a browser download, cloud backup or another application’s update traffic.
Work through a hypothetical total
Suppose the observed download rate is 10megabytes per second while a player and a separate file download are active. That total cannot be assigned entirely to the programme without another measurement. Even if the player is the only visible window, background applications can still contribute. Keep the unit distinction as well: megabytes per second and megabits per second differ by a factor of eight before other measurement details are considered.
Make the comparison useful
Record the active task and interval, pause a nonessential unrelated transfer through its normal controls if appropriate, and repeat the same authorised viewing action. A reduction in total traffic can be an observation to investigate, but it does not directly establish the media’s encoded bitrate or which server request stalled. Preserve the actual player error or visible symptom alongside the resource chart.
Avoid turning correlation into attribution
A graph rising when playback begins suggests associated activity, but it is still necessary to know what the tool counts. Do not call a system aggregate a captured video-packet measurement or a UK IPTV delivery-speed test. Label it as system network activity and state the limits. That makes the evidence useful without pretending the chart identifies every application’s contribution.