| User | Post |
Jesper
Posts: 1444/2390 |
Originally posted by Zem
And the servers that don't support it are the guy with the shotgun who doesn't like people who ask for too much.
Yep. |
Zem
Posts: 495/1107 |
Originally posted by Jesper
HTTP Pipelining is just sending multiple requests through the same connection. Imagine a guy needing to get A, B and C from the same guy. The normal way of doing that from the browser's point of view would be to knock on the door, say "Hi, I need A, could I get that?", get A, say goodbye and then close the door, and repeat the process for B and C. Pipelining is just saying "Hey, you know, I need A, B and C." and receiving all three at once.
And the servers that don't support it are the guy with the shotgun who doesn't like people who ask for too much. |
Jesper
Posts: 1439/2390 |
In case anyone's wondering, the paint delay is there to make sure you don't see a "half baked" page. The trade-off, obviously, is a slightly less responsive browser.
HTTP Pipelining is just sending multiple requests through the same connection. Imagine a guy needing to get A, B and C from the same guy. The normal way of doing that from the browser's point of view would be to knock on the door, say "Hi, I need A, could I get that?", get A, say goodbye and then close the door, and repeat the process for B and C. Pipelining is just saying "Hey, you know, I need A, B and C." and receiving all three at once. |
FreeDOS
Posts: 954/1657 |
Most servers should though. Think of things like GameFAQs where literally thousands upon thousands of people are reaching the site simutaniously.  |
HyperLamer
Posts: 2641/8210 |
I think the reason this stuff is disabled is that not all servers support it very well. But hell, I'll do it anyway. 
Hmm, my MaxRequests (in Mozilla) is set to 4. I like 50 better. 
Holy crap, that is fast!  |
Emptyeye
Posts: 1175/2273 |
Hmm, it appears I made these tweaks already. This along with DSL explains why Firefox is nice and fast.
Only difference is I set maxrequests to 100. |
windwaker
Posts: 778/1797 |
I already searched . I couldn't really find anything (save the one you already showed). |
FreeDOS
Posts: 948/1657 |
Unfortunately, this is the only tweak that I know... besides this, I'm using vanilla Firefox (with an exception of a theme, custom toolbar, and extensions. Those don't count ). However, searching Firefox Tweak and Firefox Tweaks on Google seems to bring up things. |
windwaker
Posts: 773/1797 |
Do you know of any other Firefox tweaks? It seems like there's got to be more. This's great.
Edit: there's an extension that'll do this.
https://addons.update.mozilla.org/extensions/moreinfo.php?application=firefox&id=327&vid=989 |
FreeDOS
Posts: 947/1657 |
Yeah, I doubt it's an OS thing, but you may never know
Leg: What kind of rendering fixes do you mean? I don't see a problem at all.... Of course, if you know C++, you can always fix it whenever |
Legion
Posts: 3364/5657 |
Hmm, maybe with this little tweak it will be faster than IE. If not more so.
Now, got any fixes for table rendering? >=D |
Ailure
Posts: 6853/11162 |
Actually it's not slowing the thing down, and I doubt that Firefox really differs that much from the OS's. Firefox in Linux is pretty much the same when youre using it and how it works. I do know since I have Linux on one of my computers.
Setting "nglayout.initialpaint.delay" to 0 didn't slow this computer down. But I test it with my extremly picky 400 mhz and see if it slows that one down. I doubt it's a OS thing...
I'm not sure how much effect that pipelining have thought. But I did notice a diffrence with changing the delay.
Edit: However, a certain graphic heavy Swedish newssite loaded alot faster than usual. So it probably had that effect... |
Karadur
Posts: 413/1192 |
Originally posted by FreeDOS
Well... I'm using a Cely 1.4 GHz and it doesn't slow down my PC. hmm... perhaps it's a Windows thing (I use Slackware Linux)?
My processor's an AMD Athlon XP 2GHz, and there hasn't been any noticeable slowdown since I changed those options. Like Ailure and windwaker, I thought Firefox was nice and quick before, but now it's even better Thanks again  |
windwaker
Posts: 769/1797 |
Firefox is really fast for me (perhaps because I have some great RAM), but MAN this made it fast. Thanks . |
FreeDOS
Posts: 946/1657 |
Well... I'm using a Cely 1.4 GHz and it doesn't slow down my PC. hmm... perhaps it's a Windows thing (I use Slackware Linux)?
nglayout.initialpain.delay doesn't seem to affect this board much, probably the extremely sloppy HTML.
I'm not sure why this isn't default... but I know that the Mozilla Foundation doesn't always make good choices (Firefox becoming 1.0 should have come by later when more bugs are fixed; all projects' sources are in one tree). |
Ailure
Posts: 6848/11162 |
Keep in mind that changing "nglayout.initialpaint.delay" to 0 can slow your computer down some. Especially if it's old. At least that's what I heard from other persons.
I try this out at least, if anything I could just set it back later on. If it's that's good, why isn't it default? Is it something that's in beta or?
Edit: Heh, it's quite alot faster now after loading a few pages and such. Firefox was faster than IE before for me but now... wow. o.o And I really don't notice any slowdowns with having "nglayout.initialpaint.delay" on zero, but I test that on a older computer... |
Karadur
Posts: 410/1192 |
Nice trick to make things faster I think I saw something similar to this on some other site dealing with Firefox or Firebird, but I could never remember where exactly it was. This appears to work just as well though.
I obviously use Firefox too, so thanks for the tip  |
FreeDOS
Posts: 945/1657 |
Ok... here we go. I've always liked Firefox, but not the slowness. I found out how to make it fly
- Type "about:config" into the URL bar and hit return. Scroll down and look for the following entries:
- network.http.pipelining
- network.http.proxy.pipelining
- network.http.pipelining.maxrequests
Normally the browser will make one request to a web page at a time. When you enable pipelining it canl make several at once, which really speeds up page loading. - Alter the entries as follows: (by double clicking them)
- Set "network.http.pipelining" to "true"
- Set "network.http.proxy.pipelining" to "true"
- Set "network.http.pipelining.maxrequests" to some number like 40. This means it can make 40 requests at once.
- Right-click anywhere and select New -> Integer. Name it "nglayout.initialpaint.delay" and set its value to "0". This value is the amount of time the browser waits before it acts on information it recieves in milliseconds. Normally, Firefox takes 250 ms (1/4 second) to render anything.
|
