daily pastebin goal
55%
SHARE
TWEET

Untitled

a guest Jul 7th, 2018 3 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. 18:34 -!- tc424 [~steved@2001:470:1f1d:e3b::34] has joined #winswitch
  2. 18:34 -!- Topic for #winswitch: winswitch 0.12.23 | xpra 2.3.2 | please try updating to the newest version before reporting bugs
  3. 18:34 -!- Topic set by totaam [~antoine@users.devloop.org.uk] [Tue Jun 26 19:01:38 2018]
  4. 18:34 [Users #winswitch]
  5. 18:34 [@totaam    ] [ Benjojo ] [ davidl_   ] [ icasdri  ] [ qyliss     ] [ tc424    ]
  6. 18:34 [ [Neurotic]] [ bolt    ] [ docmax    ] [ idupree7 ] [ raso2      ] [ tribut   ]
  7. 18:34 [ `brain`   ] [ Boobuigi] [ ds_shadof ] [ izibi    ] [ rootman    ] [ tsto     ]
  8. 18:34 [ akaWolf   ] [ bug2000 ] [ early     ] [ jbrett   ] [ rudi_s     ] [ wodencafe]
  9. 18:34 [ Akronym   ] [ CcxWrk  ] [ elibrokeit] [ kugel    ] [ shadoxx    ] [ yomii    ]
  10. 18:34 [ amir      ] [ Chaz6   ] [ EliDupree ] [ luke-jr  ] [ smo        ]
  11. 18:34 [ aterius   ] [ copec   ] [ femme     ] [ mtgx`    ] [ Some_Person]
  12. 18:34 [ atrus     ] [ darvon  ] [ grazzolini] [ ohama    ] [ stux       ]
  13. 18:34 [ Avengence ] [ davidl  ] [ hosenknopf] [ pfallenop] [ tbr        ]
  14. 18:34 -!- Irssi: #winswitch: Total of 50 nicks [1 ops, 0 halfops, 0 voices, 49 normal]
  15. 18:34 -!- Channel #winswitch created Wed Nov  2 07:11:40 2011
  16. 18:34 -!- Irssi: Join to #winswitch was synced in 1 secs
  17. 18:36 < tc424> hi all, new to xpra, have installed latest version on server (ubuntu 16.04) and client (18.04), but a bit surprised at the latency versus direct X forwarding, given this is 1Gb/s connection
  18. 18:37 < tc424> forcing rgb/png helps a bit, but not as much as I'd hoped, and I don't know why it's not picked automatically given link speed. anything obvious I may have overlooked?
  19. 18:39 <@totaam> tc424: set --speed=100 instead
  20. 18:39 <@totaam> or force just rgb
  21. 18:39 <@totaam> there should be zero latency on a gigabit link
  22. 18:40 <@totaam> except for link latency itself, obviously
  23. 18:41 < tc424> ah, will try that, thanks - was a bit shocked when moving from flaky wifi to ethernet didn't seem to help!
  24. 18:43 <@totaam> wifi is usually terrible, but better in 2.4
  25. 18:43 <@totaam> latency jitter is hard to deal with
  26. 18:43 <@totaam> on ethernet gigabit, you can forward 4k windows as long as they don't update too quickly
  27. 18:43 <@totaam> for 4k video, you need hardware encoding
  28. 18:44 < tc424> ok, got --speed=100, was briefly ok when I first connected, now seem frame delay around ~250ms!
  29. 18:44 < tc424> something is obviously really wrong :(
  30. 18:44 <@totaam> that's definitely not right
  31. 18:45 <@totaam> tc424: see http://xpra.org/trac/wiki/ReportingBugs
  32. 18:46 <@totaam> those are the kinds of details we need to investigate anything
  33. 18:46 < tc424> thanks, it could be something local, my machines tend to end up a bit hacked up, but the client machine at least should be pretty clean
  34. 18:46 < tc424> it's basically an Intel SoC box being used as an X terminal
  35. 18:47 <@totaam> SoC - as in low power?
  36. 18:48 < tc424> yeah, fairly
  37. 18:48 < tc424> but fully accelerated gfx
  38. 18:48 < tc424> seeing may 10-20% cpu utilization
  39. 18:49 < tc424> straight X using XDMCP is fine, pretty much indistinguishable from the "server" console
  40. 18:50 <@totaam> tc424: make sure opengl rendering is enabled
  41. 18:50 < tc424> I /think/ it is
  42. 18:50 <@totaam> it should say in the client output
  43. 18:50 < tc424> 2018-07-07 18:42:28,299 OpenGL enabled with Mesa DRI Intel(R) HD Graphics 500 (Broxton 2x6)
  44. 18:50 < tc424> 2018-07-07 18:42:27,684 No OpenGL_accelerate module loaded: No module named OpenGL_accelerate
  45. 18:50 < tc424> 2018-07-07 18:42:28,241 Warning: vendor 'Intel Open Source Technology Center' is greylisted,
  46. 18:50 <@totaam> OK, then it is
  47. 18:50 <@totaam> I'm out of ideas
  48. 18:51 <@totaam> 250ms is way too much
  49. 18:51 < tc424> now at 875ms!
  50. 18:51 < tc424> the batch delay keeps climbing
  51. 18:51 <@totaam> please file a ticket
  52. 18:51 <@totaam> with at least "xpra info"
  53. 18:52 < tc424> OK, will do, is there a way to monitor  batch delay computations in real time as they happen?
  54. 18:52 <@totaam> "-d stats" will show more details
  55. 18:52 <@totaam> (server side)
  56. 18:52 <@totaam> it's not very readable
  57. 18:52 <@totaam> coule be bandwidth limits triggering it
  58. 18:53 <@totaam> try adding --bandwidth-limit=0
  59. 18:53 < tc424> will do, it's not set according to the GUI, but just in case...
  60. 18:57 -!- docmax1 [~docmax@x4e3376e8.dyn.telefonica.de] has joined #winswitch
  61. 19:00 -!- docmax [~docmax@x55b26367.dyn.telefonica.de] has quit [Ping timeout: 256 seconds]
  62. 19:00 -!- docmax1 is now known as docmax
  63. 19:05 < tc424> OK I see the same thing just running the client + server on the same machine ..
  64. 19:06 < tc424> network 1-3ms, damage ~90ms, batch ~110ms
  65. 19:25 <@totaam> tc424: running on the same machine should use mmap, which means all delays should be near zero there
  66. 20:54 -!- Boobuigi [~weechat@unaffiliated/boobuigi] has quit [Ping timeout: 240 seconds]
  67. 21:31 -!- Boobuigi [~weechat@unaffiliated/boobuigi] has joined #winswitch
  68. 21:33 < tc424> totaam: yeah, that's what I thought :(
  69. 21:51 < tc424> totaam: will open proper ticket tomorrow hopefully when brain is less broiled, but in the meantime https://pastebin.com/nuZjFBH0 shows the escalating batch delay
  70. 21:53 < tc424> 2018-07-07 21:38:29,099 record_latency: took 2098.1 ms round trip, 2098.1 for echo,  285.0 for decoding of      273 pixels,     1145 bytes sent over the network in 1813.0 ms, 1813.0 ms for echo
  71. 21:53 < tc424> ..that doesn't look healthy..
  72. 22:11 -!- davidl_ [~usrname@fsf/member/usrname] has quit [Ping timeout: 265 seconds]
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top