-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shadow/seamless debugging latency #2617
Comments
2020-03-03 20:32:17: stdedos uploaded file
|
2020-03-03 20:32:26: stdedos uploaded file
|
2020-03-03 20:32:35: stdedos uploaded file
|
2020-03-03 20:32:44: stdedos uploaded file
|
2020-03-03 20:32:54: stdedos uploaded file
|
2020-03-03 20:34:57: stdedos commented
|
Fixed in r25485.
Please attach
That's not normal at all.
That has been fixed in r25463 and tested repeatedly on a blank win10 VM, again today with r25483.
I don't understand. You should now have permission to edit the ticket yourself. |
2020-03-04 05:43:48: stdedos commented
|
r25486 moves the IO to a thread, but the
Done for all platforms in r25487 |
2020-03-05 21:24:37: stdedos commented
|
2020-03-31 11:38:23: stdedos commented
|
2020-03-31 11:38:45: stdedos uploaded file
|
2020-03-31 11:38:56: stdedos uploaded file
|
2020-03-31 11:57:52: stdedos uploaded file
|
2020-04-16 08:24:40: stdedos commented
|
2020-04-17 14:58:33: stdedos commented
|
2020-04-17 14:58:48: stdedos uploaded file
|
2020-04-17 14:59:01: stdedos uploaded file
|
2020-04-22 14:57:10: antoine commented
|
2020-04-23 08:38:05: stdedos commented
|
2020-04-23 08:38:18: stdedos uploaded file
|
2020-04-23 08:38:27: stdedos uploaded file
|
2020-04-23 08:38:38: stdedos uploaded file
|
From the graphs on comment:11, your server latency spiked to 48 seconds! I would need to be able to reproduce the problem to have a chance to fix this. |
2020-04-23 11:34:38: stdedos commented
|
Wouldn't it be better to just show the bandwidth in bps? (Mbps / Kbps) And leave the pixels/s alone. Is that what you mean by dual-axis?
It should. I don't understand why it doesn't.
Try Two more things worth trying:
Important: do this locally, env vars are not forwarded with ssh remote starts. |
2020-04-28 18:05:28: stdedos commented
|
2020-04-29 08:06:17: stdedos commented
|
It should. You can verify it did get applied with
That's weird, r26192 converts this to a warning. |
2020-04-29 08:41:51: stdedos commented
|
Are you sure that you applied the environment variables separately and correctly? With |
2020-05-05 11:54:57: stdedos commented
|
Please include the full |
2020-05-15 09:57:50: stdedos commented
|
2020-05-15 09:58:07: stdedos uploaded file
|
2020-06-04 10:32:49: stdedos commented
|
2020-06-04 10:33:03: stdedos uploaded file
|
2020-06-04 10:33:13: stdedos uploaded file
|
2020-06-04 10:33:21: stdedos uploaded file
|
2020-06-04 10:51:06: antoine commented
|
2020-06-04 11:00:30: stdedos commented
|
2020-06-04 16:11:38: stdedos commented
|
2020-06-04 16:11:55: stdedos uploaded file
|
2020-06-04 16:14:16: stdedos uploaded file
|
2020-06-08 14:52:04: stdedos commented
|
2020-10-26 14:10:42: stdedos commented
|
2020-10-26 14:11:11: stdedos uploaded file
|
2020-10-26 14:11:21: stdedos uploaded file
|
#2421 may help us spot bandwidth issues earlier |
2020-11-23 23:15:55: stdedos commented
|
Actual link: XPRA performance on jittery and droppy connections. This is the last blocker ticket I am looking to before releaseing 4.0.6 and then 4.1. It is tracked in various tickets, the current one I am using to record progress is : #2812. |
Issue migrated from trac ticket # 2617
component: client | priority: major
2020-03-03 20:31:54: stdedos created the issue
The text was updated successfully, but these errors were encountered: