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 :
1 tab – msn.com
2 tabs – msn.com | facebook.com/xenappblog
3 tabs – msn.com | facebook.com/xenappblog | twitter.com/xenappblog
In total memory per user this would be in the correct order : 71mb / 111mb / 154mb
So with only one simple registry setting we can limit Internet Explorer to only run one instance of iexplore.exe for the frame and one for the tabs. This is a REG_DWORD key located under HKCU. For full details check out this MSDN blog post : Opening a New Tab may launch a New Process with Internet Explorer 8.0.
The numbers speak for themselves : 52mb / 62mb / 80mb. I encourage you to check it out right away, and yes it would also work on you personal computer with IE8.
Some other things to keep in mind in terms of Internet Explorer 8 :
- Add-ons add load times every time you open a new browser window or tab
- Keep restriced or trusted site zone list to a minimum
- Keep add-ons and plug-ins up to date. e.g older versions of Adobe Flash may result in browser crashes or hang