Opened 20 months ago
Last modified 3 months ago
#2382 assigned defect
memscroller stresses the html5 client
| Reported by: | Antoine Martin | Owned by: | Antoine Martin |
|---|---|---|---|
| Priority: | major | Milestone: | 4.2 |
| Component: | html5 | Version: | 2.5.x |
| Keywords: | Cc: |
Description (last modified by )
Split from #2231, see ticket:2231#comment:9.
Damage latency goes up to 7 seconds with chrome!
Average is also too high:
Attachments (2)
Change History (10)
Changed 20 months ago by
| Attachment: | memscroller.png added |
|---|
comment:1 Changed 20 months ago by
| Description: | modified (diff) |
|---|---|
| Status: | new → assigned |
comment:2 Changed 20 months ago by
More test data showing the memscroller outlier problem in ticket:2231#comment:12.
comment:3 Changed 20 months ago by
As per ticket:619#comment:29, the problem occurs only with NODELAY=0.
My guess is that this buffers too many packets in the kernel's socket output buffer, allowing things to spiral out of control.
Changed 20 months ago by
| Attachment: | memscroller-server-rss.png added |
|---|
memscroller also uses too much memory
comment:5 Changed 20 months ago by
| Milestone: | 3.0 → 4.0 |
|---|
As per comment:3 and ticket:2231#comment:12, the default configuration handles this well enough that this can wait for the next release.
comment:6 Changed 13 months ago by
| Milestone: | 4.0 → 4.1 |
|---|
comment:7 Changed 6 months ago by
| Milestone: | 4.1 → 4.2 |
|---|
comment:8 Changed 3 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2382
Note: See
TracTickets for help on using
tickets.
copyleft 2010 - 2021
memscroller latency