It's stuff like this that makes me wish IIS had a mechanism to set the max connections per user like Apache does.
8 persistent connections isn't too horrible on the web server but there's no need for that many. 2 or 4 should be more than enough. 64 max connections is just silly unless you are superhuman and somehow able to browse/load 8 or more different pages in different tabs simultaneously.
I'd prefer that users don't hit our site this hard but there's little I can do about it.
Drew, Other than the 2 to 4 persistent connections, can you recommend values for the other settings that will allow for a balance between improved Firefox performance and server resources?
Seconded, since this is something I know jack about. I use Firefox to connect to my job, so speeding it up would be useful, but I don't want to bog other people down in the process (well, maybe the corporate guys).
[Link]
nietzsche Deactivated User
5470 Posts 8/03
Posted - Apr 15 2007 : 8:15PM
I made the recommended changes and it's had the opposite effect. I'm going back to the way it was.
I made the dialup changes and I'm not seeing any difference. What do those settings change, anyway? I recall some of these tweaks would cause your browser to load ahead, or preload things linked in the current page, but I don't see how pre-loading one hundred pages is going to speed up the one page I want to see.