I am developing on SharePoint 2013 Windows 2008 R2
I have more than adequate hardware (i.e. 16 cores, 48GB RAM, very fast SAN SSD hard disks). The issue I am having is NOT a hardware issue
When I open a document library in Internet Explorer 10, performance is adequate (although not very fast) provided that I makecontinual use of the interactive session by clicking on something and browsing around my sites without waiting for more than 20 seconds or so.
If I wait any longer (e.g. 2 mins) and click on something, NOTHING happens. The IE spin icon just spins and spins and spins as if there is no response from the Server whatsoever. When this happens, there is no noticeable increase in activity amongst the running processes in Resource Monitor and certainly no overall CPU spike
If I then open a new Browser (and it must be a new browser instance, rather than a new tab) and access exactly the same link that was failing to respond in my previous browsing session, it will work as expected.
I'm assuming this is some kind of timeout issue although I have not ruled out the possibility of a specific problem with IE 10 by trying other browsers. If this is a timeout issue, it must be a very low timeout threshold
Having to start a new IE session every 5 minutes or so, just so that I can test changes or refresh a library, is driving me nuts. More pertinently, when we move to a production environment, my end users will simply not tolerate such a fundamental flaw
Does anyone know where I can begin to look for the timeout settings that will clear this issue up and eradicate the problem?
thanks