Xpra: Ticket #2231: automated tests should be able to test html5 client

And record the client type so we can compare python vs html5.

Thu, 21 Mar 2019 01:08:58 GMT - Antoine Martin: priority, status changed

Blocker for #2232.

Thu, 04 Apr 2019 02:58:00 GMT - Antoine Martin:

Blocked by #2251

Tue, 23 Apr 2019 10:04:21 GMT - Antoine Martin: owner, status changed

Working OK now that #2251 is fixed + minor fixes from r22517.

With one important caveat: the browser session must not be resumed from an earlier one as this would interfere with the testing, so one has to use a profile specifically setup for this testing. Either a brand new user, or forcing a new profile:


@encodedEntropy: I think there's enough there to hand over to you, let's get some data and iterate.

Thu, 01 Aug 2019 11:59:56 GMT - Smo: owner changed

Wed, 07 Aug 2019 11:19:24 GMT - Smo:

Browsers are working great with automated tests. The only feedback I have is what you have said already is that we may want to set the window size but in my tests my window always starts the same size.

Firefox window seems to be a good size but the chrome one sometimes cuts off the window of the application being tested.

Not sure if this matters all that much since it is the same size every time.

Wed, 07 Aug 2019 11:19:55 GMT - Smo: owner changed

Thu, 08 Aug 2019 05:37:36 GMT - Antoine Martin: owner changed

Can you post some data?

Thu, 08 Aug 2019 16:14:37 GMT - Smo: owner changed

I'm attaching some perf tests comparing firefox and chrome. I wanted to compare them with the python2 client as well but the data doesn't seem to line up.

Thu, 08 Aug 2019 16:14:56 GMT - Smo: attachment set

Compare firefox and chrome with charts

Sun, 11 Aug 2019 06:19:39 GMT - Antoine Martin: owner changed

Interesting data points:

Can you post some comparison of python vs html5? On auto, so we can see the gap in performance. (then I think we can close this ticket)

Wed, 14 Aug 2019 00:22:39 GMT - Smo: attachment set

compares all clients

Wed, 14 Aug 2019 00:23:57 GMT - Smo:

Attached is a comparison of all the 3 clients. I had the data before but I had to fix the script for the charts to compare them.

Also changed the css a bit to be able to read things.

Wed, 14 Aug 2019 00:24:10 GMT - Smo: owner changed

Wed, 14 Aug 2019 06:31:21 GMT - Antoine Martin: attachment set

average batch delay

Wed, 14 Aug 2019 06:31:33 GMT - Antoine Martin: attachment set

regions per second

Wed, 14 Aug 2019 06:33:30 GMT - Antoine Martin: status changed; resolution set

Also changed the css a bit to be able to read things.

Nice, thanks!

First thing to mention is that the decoding-pixels-per-second values for the html5 client are wrong: javascript is not decoding 50GPixels per second! (nothing can - I will try to fix it)

As expected, the python client is way ahead of the html5 client:

average batch delay regions per second

That said, the html5 client does better than I thought it would do. (it is sacrificing framerate and quality in the pure-video glxgears test - but managing OK) Also interesting to see that Firefox does quite a bit better than Chrome overall.

Wed, 21 Aug 2019 07:59:45 GMT - Antoine Martin:

Fix for the decoding latency reported by the html5 client: r23551.

Sat, 30 May 2020 04:58:11 GMT - Antoine Martin:

r23551 was completely wrong: both Date.now return time values in milliseconds! r26526 reverts it.

Sat, 23 Jan 2021 05:45:41 GMT - migration script:

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