xpra icon
Bug tracker and wiki

Opened 12 days ago

Last modified 4 hours ago

#2381 new task

add total latency to perf charts

Reported by: Antoine Martin Owned by: Smo
Priority: major Milestone: 3.0
Component: tests Version: 2.5.x
Keywords: Cc:

Description (last modified by Antoine Martin)

As part of #619 and #2130, it would help to be able to see how long screen updates take to land on the client's screen.
In the same way that we have the "overall latency" on the session info graphs.

Attachments (1)

test_nodelay0cork0.tar.gz (238.0 KB) - added by Smo 4 hours ago.
nodelay0 cork0 vs defaults

Download all attachments as: .zip

Change History (5)

comment:1 Changed 36 hours ago by Antoine Martin

Description: modified (diff)
Status: newassigned

comment:2 Changed 19 hours ago by Antoine Martin

Owner: changed from Antoine Martin to Smo
Status: assignednew

r23539 records two new attributes in xpra info:

  • client.damage.frame-total-latency: how long it takes from the moment we get a damage event until we get the draw acknowledgement packet from the client, that's everything we do - which can be summarized as: batch delay + compression + sending + network latency + receiving + updating the window buffer + sending ack + network latency (again) + receiving ack
  • client.damage.client-latency: same, minus the connection latency (note: this latency includes the cost of the protocol layer - which is small in most but not all cases..)

As of r23541, these new attributes are now exposed in the perf test data as:

  • "Frame Total Latency"
  • "Client Frame Latency"

@smo: does that work?
Maybe re-run just NODELAY=0 + CORK=0 vs default settings.

comment:3 Changed 14 hours ago by Smo

Added these to charts in r23546

Changed 4 hours ago by Smo

Attachment: test_nodelay0cork0.tar.gz added

nodelay0 cork0 vs defaults

comment:4 Changed 4 hours ago by Smo

Here are the results attached to the ticket.

Something looks off to me what do you think?

Note: See TracTickets for help on using tickets.