|
For those using Firefox... (pg. 3)
|
View this Thread in Original format
| Emil |
| quote: | Originally posted by Ken_Allen
*hands Emil a fully loaded high powered shotgun* |
Thank you. Will you come to my funeral? |
|
|
| Greedy |
thanks!
where did u get this info? |
|
|
| JMF [TrAcId] |
thanks for that!
the increase is very noticeable! :disbelief |
|
|
| Lira |
| quote: | Originally posted by JMF [TrAcId]
the increase is very noticeable! :disbelief |
Indeed, thank you very much :) |
|
|
| Lil-H |
| and where is this stuff for opera? |
|
|
| Chris d(-_-)b |
| Thanks a bunch, but any ideas how to do this with IE? |
|
|
| Cloudburst |
| I think it's slower now hehe, now it waits for like ½ second before anything happens... I had instant page display before with opera anyway.. :p |
|
|
| Roquer |
| quote: | Originally posted by Elmo-On-XTC
Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.[quote]
No point in setting this over 8, as 8 is the maximum value that is acceptable.
[quote]
3. Lastly 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 receives. |
Only do this if you have a fast PC. Rendering in realtime is far slower if you lack the CPU power. If you are running with less than 1.5 mhz, I recommend setting it to 4000 or so. Experiment and find what is best for you. |
|
|
|
|
