This is a follow up post for Why Internet Explorer will kill your memory – Part I that I published in March this year. A lot of people have been requesting this and I’m sorry for keeping you waiting so long. I think the reason why this post have been delayed is that I’ve been putting to much into it. I wanted it to cover everything; Internet Explorer 8 tuning, Citrix HDX MediaStream for Flash and so on. Well I just figured out let’s take the IE8 tuning in Part II and then the rest of the stuff can come in some other series.
The setting I’m about to reveal for you will save you a big chunk of memory and money, in both XenApp and XenDesktop environments. By default, IE8 will start with two instances of iexplore.exe (one for the Frame, one for the tab) and grows the number of tab processes as needed based on the amount of available RAM, the number of tabs, the integrity levels for tabs, and the number of distinct IE sessions. Let’s take a look at some examples :
