https://gerrit.wikimedia.org/r/#/c/218006/ has brought along big performance issues on IE, while everything runs fine in Chrome and Firefox.
It's unclear what the issue is, but http://stackoverflow.com/a/30444081/1393377 has some hints.
https://gerrit.wikimedia.org/r/#/c/218006/ has brought along big performance issues on IE, while everything runs fine in Chrome and Firefox.
It's unclear what the issue is, but http://stackoverflow.com/a/30444081/1393377 has some hints.
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
JS performance optimization | labs/tools/crosswatch | master | +213 -79 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Sitic | T99930 Minimum viable product [tracking] | |||
Resolved | Sitic | T100341 Improve design | |||
Declined | None | T102569 Performance issues on IE due to layout attributes in angular-material.css |
Change 219477 had a related patch set uploaded (by Sitic):
JS performance optimization
After some time debugging it and a lot of JS performance improvements it might actually be some rendering issue in IE, and not something related to the two-way data binding. The "UI Responsiveness" debugger in IE shows that it spends most of its time when it blocks in "Style calculation".
It might be some issue with flexbox (which is somewhat strange in IE anyway) because of which it spends most of its time rendering. I'm still investigating, there are a lot of bug reports for these kinds of issues, but I didn't see a current one so far.
IE has problems rending even 50 watchlist events at once, while Chrome does ~1000 easily.
Is a lot better now (but still freezes for 1-2 sec on watchlist rendering). Seems to be related to
The problem definitely is caused by layout attributes implemented by angular-material.css. This bug is stalled until it is fixed upstream.
@Sitic: I am resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!). Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task. Please claim this task again when you plan to work on it (via Add Action... → Assign / Claim in the dropdown menu) - it would be welcome! Thanks for your understanding.
https://github.com/angular/material/issues/3455 and https://github.com/angular/material/issues/1771 were closed by merged https://github.com/angular/material/pull/4282 hence resetting task status to open.
Crosswatch seems unmaintained and inactive (see T269703). You may want to use https://meta.wikimedia.org/wiki/Special:GlobalWatchlist instead.