Post by Pasta Sauce on Oct 17, 2005 9:08:49 GMT -8
BEFORE READING, READ THIS FIRST!
slacy.com/blog/index.php/2005/06/13/http-pipelining-considered-harmful/
make a new tab and in the adress bar type:
about:config
a filter bar should be there underneath yhour address bar.
go ahead and save yourself some searching by typing:
pipe
three things should appear.
Change network.http.pipelining to true, and same for network.http.proxy.pipelining.
Changing network.http.pipelining.maxrequests to some number, probably around 20-30.
It should look like this:
Last step:
right click, goto new, integer
name it this:
set it to zero.
there are some negative effects to pipelining as I mentioned before.
Edit: Didn't get to finish this tut before class got over but it is finished now.
slacy.com/blog/index.php/2005/06/13/http-pipelining-considered-harmful/
make a new tab and in the adress bar type:
about:config
a filter bar should be there underneath yhour address bar.
go ahead and save yourself some searching by typing:
pipe
three things should appear.
network.http.pipelining -- False
network.http.pipelining.maxrequests -- 4
network.http.proxy.pipelining -- False
Change network.http.pipelining to true, and same for network.http.proxy.pipelining.
Changing network.http.pipelining.maxrequests to some number, probably around 20-30.
It should look like this:
network.http.pipelining -- True
network.http.pipelining.maxrequests -- 30
network.http.proxy.pipelining -- True
Last step:
right click, goto new, integer
name it this:
nglayout.initialpaint.delay
set it to zero.
there are some negative effects to pipelining as I mentioned before.
Edit: Didn't get to finish this tut before class got over but it is finished now.
