Networked-Aframe Performance Benchmark

Entities: 0

Updates/sec (sent): 0

Updates/sec (received): 0

Messages/sec (sent): 0

Messages/sec (received): 0

Network Latency: 0 ms

Bytes/sec (sent): 0 KB/s

Bytes/sec (received): 0 KB/s

Round-trip Time: 0 ms

Peer RTT avg (client to client): —

Peer ping target: —

Open two browsers in the same room. Peer RTT uses NAF.connection.sendData echo: on adapters with a WebRTC data channel it is peer-to-peer; on native WebTransport or Socket.IO it is relayed client→server→client (expect higher RTT than P2P). The Round-trip Time row above is still client→server (e.g. getServerTime), not peer RTT.

Synchronization Metrics

Connected Clients: 0

Update Propagation Time: 0 ms

Sync Latency (avg): 0 ms

Updates in Queue: 0

Sync Success Rate: 100%

Test Controls

Entity Count:

Update Rate (ms):

Bulk Update Test

Bulk Size:

Bulk Updates Sent: 0

Stress Tests

Maximum Updates Test

Duration (seconds):

Throughput Test

Duration (seconds): Message Size (bytes):

Latency Under Load Test

Duration (seconds): Load Level (concurrent pings):

Network Performance Chart

Messages/sec Latency (ms) Throughput (KB/s)

📊 Performance Benchmark - WebTransport WebRTC