Xpra: Ticket #2381: add total latency to perf charts

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.

Mon, 19 Aug 2019 16:38:36 GMT - Antoine Martin: status, description changed

Tue, 20 Aug 2019 10:25:35 GMT - Antoine Martin: owner, status changed

r23539 records two new attributes in xpra info:

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

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

Tue, 20 Aug 2019 14:48:23 GMT - Smo:

Added these to charts in r23546

Wed, 21 Aug 2019 00:41:19 GMT - Smo: attachment set

nodelay0 cork0 vs defaults

Wed, 21 Aug 2019 00:42:12 GMT - Smo:

Here are the results attached to the ticket.

Something looks off to me what do you think?

Wed, 21 Aug 2019 05:16:20 GMT - Antoine Martin: attachment set

debug client frame latency

Wed, 21 Aug 2019 05:20:48 GMT - Antoine Martin:

Something looks off to me what do you think?

Yup. The values are completely wrong: they should usually be lower than 100ms (+network latency). No idea why. The values are correct when I run xpra info | egrep "damage.frame-total|damage.client-latency" and the perf test code uses the same function as everywhere else for capturing the data:

add("", avg, "Frame Total Latency",             ["client.damage.frame-total-latency"])
add("", avg, "Client Frame Latency",            ["client.damage.client-latency"])

I've also run the tests and got sensible values out:

Frame Total Latency	 Client Frame Latency
34	34
43	43
45	45
32	32
77	77
63	63

Can you run again with the patch attached and see what you get? It will dump the values it finds for "Client Frame Latency" as it goes along.

Fri, 20 Sep 2019 07:20:02 GMT - Antoine Martin: milestone changed

Wed, 12 Feb 2020 05:21:09 GMT - Antoine Martin: status changed; resolution set

Sat, 23 Jan 2021 05:49:46 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2381