KTamas Posted August 18, 2005 Share Posted August 18, 2005 (edited) Hi So, I have just re-installed my windows (it was about a year old and hell slow...you know). The setup is: Windows XP Professional (yes, legal) + SP2 slipstreamed + nLite-ed (few tweaks, no msn explorer etc.). After the install, and autopatcher/windows update, of course the first thing i was installed is the latest nightly Deer Park Alpha 2. Pipelining on of course, tweaking the connection numbers etc., lets start browsing. Everything is slow and laggy. Of course, if i start to download something, it comes with full speed, but standard browsing is slooooooooooooooooooooooow. Sometimes it starts to load a page and suddenly stops and never finishes it. Sometimes it loads nothing and i have to restart it to work again. Sometimes i have to restart windows to get it to work again. I even tried the offical 1.06 release, and i got the same result, I turned off pipelining, still the same. What the heck is the problem??? Now i'm still running my old system, which is XPSP2 and has no problems... (okay, maybe i dont have all the security patches and it is not nLite-ed, but anyways...) Thanks for the help, KTamas P.S: Yes, it is fresh profile, I only copied my bookmarks in. Edited August 18, 2005 by KTamas Link to comment Share on other sites More sharing options...
BillyConnely( hehe ) Posted August 18, 2005 Share Posted August 18, 2005 Have you ran a virus scan :whistle: Link to comment Share on other sites More sharing options...
KTamas Posted August 18, 2005 Author Share Posted August 18, 2005 Have you ran a virus scan :whistle: 586395142[/snapback] This can't be a virus. IE6 works properly. Link to comment Share on other sites More sharing options...
supernova_00 Posted August 18, 2005 Share Posted August 18, 2005 its probably the pipelining or one of the other network tweaks...you probably set it wayy to high like most people do and that actually causes slower browsing. either that or you changed the nglayout.initialpaint.delay in about:config to something absurd like under 500 default is 1000 so lowest you should have is around 700 Link to comment Share on other sites More sharing options...
KTamas Posted August 18, 2005 Author Share Posted August 18, 2005 its probably the pipelining or one of the other network tweaks...you probably set it wayy to high like most people do and that actually causes slower browsing. either that or you changed the nglayout.initialpaint.delay in about:config to something absurd like under 500 default is 1000 so lowest you should have is around 700 586395684[/snapback] What are the optimal settings? I set nglayout.initialpaint.delay to 0 (or to nothing, i don't know), and all connections etc. to 100... Link to comment Share on other sites More sharing options...
supernova_00 Posted August 18, 2005 Share Posted August 18, 2005 wow that is probably why. set: nglayout.initialpaint.delay to 700 network.http.max-connections to 48 network.http.max-connections-per-server 16 network.http.max-persistent-connections-per-server to 8 network.http.pipelining to true network.http.pipelining.maxrequests to 8 those will speed it up a lot, you were really bogging down the servers and firefox with the settings you had Link to comment Share on other sites More sharing options...
Recommended Posts