P2P TC02 - Streaming Throughput (User Client)

Connect to the device, ask it (via INVITE) to stream test video with the chosen resolution / FPS / bitrate, and measure what arrives - one stream at a time, or several in parallel. Device CPU/RAM and sender stats come back over a data channel.

Signaling / ICE






STUN/TURN above and this policy are sent to the device in the INVITE
disconnected
Stream configuration (sent to the device in INVITE)



if filled, replaces the three fields above
sent to the device in the INVITE: "Off" = no audio at all, otherwise the device sends G.711 mu-law
records what the browser receives (video + audio) while the run is connected; the encoder in the browser adds some CPU load

browser senders ramp their bitrate for several seconds; the device also tunes its content

parallel: that many simultaneous streams (device --max-calls must be ≥ this)
sequential: between runs; also between profiles
parallel: delay between starting each stream



Live
-
Summary (successful runs; each value is that run's post-warm-up figure)
Success rate: -
Metricnminavgp50p95max

Runs
#ProfileResultRecv kbpsRecv fpsLoss %DroppedFreezesJitter msRTT msAudio kbpsDev CPU %Dev RSS MB
Per-second samples (current / last profile)
runt (s)kbpsfpsloss %lost (cum)dropped (cum)freezesjitter msRTT msresaudio kbpsaudio loss %audio jitter msdev CPU %dev RSS MBdev sent kbpsdev enc fpsdev droppeddev callsdev src fpsdev limit
Recordings
No recordings yet. Turn "Record received stream" on before Start.
Log