IE11 Performance in 1.0.6

[char0n]

There has been significant performance degradation in release 1.0.6 for IE 11. In 1.0.5 and IE 11 performance was not very good but it was still acceptable; but, running on 1.0.6 makes project in angular-material unusable. UI freezes and becomes irresponsible. Can you imagine some reason why there is such a dramatic performance decrease in patch version ?

Is there somebody else that have experienced something similar ?

[jpschill]

I have the same issue! When I update to 1.0.6 every user interaction (switching tabs, selecting side nav list item, scrolling in virtual repeat,…) in my app feels significantly slower in IE11 than before update. I can constantly reproduce this. When I go back to 1.0.5, the performance in IE is slow compared to Chrome/FF, but acceptable. As soon as I update to 1.0.6 the performance is, in my opinion, not acceptable anymore. So there must have been some changes in 1.0.6 that have very negative effect on IE11 performance. This is very critical to me. Since many of our customers stick with IE11, I am not able to upgrade to 1.0.6.

[char0n]

Thanks for confirming.

Related: There is an issue with Firefox, which I have addressed here: 99c9b60#commitcomment-16449602

It doesn't concern performance but applications in holy grail layout will stop working correctly. Checkout the link above for solving the problem in Firefox for 1.0.6 version.

[srweeks]

Experiencing same performance issues in IE 11 and edge

[mbeckenbach]

I can confirm, that there are massive performance issues in IE11 with 1.0.6. I have about 30% CPU while doing nothing. Edge and Chrome work fine. Same issues with 1.0.5. 1.0.0 seems to be a bit better. But is still very slow.

[kieranmcdev]

We are also seeing huge performance issues in IE11 with AM 1.0.6 which make our site unusable. 1.0.5 is much more usable in comparison, please look into these issues

[mbeckenbach]

I did some refactoring of my ng-repeats. now 1.0.5 runs is quite fast. But as soon as i update to 1.0.6 everything becomes slow

[vajnorcan]

I can confirm that it runs very slow, just open the material demo page in IE11 and see it yourself. I've deployed to windows 10 mobile and the performance is lackluster.

[david-gang]

I found out something interesting:

When we disable the css theming by setting the constant

module.constant('$MD_THEME_CSS', '');

the performance of ie gets better.

I am not sure what the reason is. Maybe it is the number of selectors. We don't know what the big O of ie is :-)

It would be interesting to hear if you also see this in your web apps.

[YoungtreeDev]

IE11 with AM 1.0.6 is pretty unusable. AM 1.0.5 was quicker by far. It seems that IE refresh isn't hitting -> does it have trouble loading the AM JavaScript or maybe just processing it? How does IE handle the cache of JS code in memory?
We've downgraded to 1.0.5 in any event. A fix for this would be great, thanks!

[vajnorcan]

@david-gang well, that helps but I've lost all the css and styling ;)
@YoungtreeDev even with 1.0.5 I wouldn't call AM a quick UI on IE Edge (!) on WM10

[jpschill]

@david-gang
With AM1.0.5 I can confirm that disable css theming has a big impact on IE11 performance. The UI feels faster/smoother. So optimizing AM´s styles for IE would be very helpful to improve IE performance in general, I think.
But with AM1.0.6 even disable css theming does not help. It feels extreme slow, with or without styles enabled.

[PeterStAngelo]

Is anyone else seeing improvements with 1.1.0 rc1 ?

[lpillonel]

Yes it is working now like before 1.0.5