We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free.


Join our community!


If you're already a member please log in to your account to access all of our features:

Username:   Password:
Add Reply
  • Pages:
  • 1
  • 2
  • 4
Making Firefox faster
Topic Started: Apr 4 2005, 12:28 AM (3,985 Views)
dbzlotrfan Apr 29 2005, 05:07 PM Post #16
Member
[ * * * * * * * ]
DuffMan
April 29, 2005 03:16 PM
SkItZo
April 29, 2005 06:49 AM
I made it 150000000 for network.http.pipelining.maxrequests is that safe for me to use? Will it crash any of the websites I'm viewing? haha

That would not be a great idea.

would you say stick with 30, or less, like 20 or 15?
Offline Profile Quote Post Goto Top
 
Seth Apr 29 2005, 05:33 PM Post #17
Member Avatar
I has a pony
[ * * * * * * * * * ]
ASDF123
April 29, 2005 04:03 PM
if you do that, you'll slow down everyone else that uses that site. and you'll slow down that site itself, sucking its bandwidth like a vampire. :smithster:

Not true. You will use the same amount of bandwidth.
Offline Profile Quote Post Goto Top
 
Deleted Account Apr 29 2005, 08:50 PM Post #18
Member
[ * * * * ]
 It does not seem faster to me. In fact, it is slower if anything. :'(

*goes to change it back*
Offline Profile Quote Post Goto Top
 
Gogf Apr 29 2005, 08:56 PM Post #19
Indescribable
[ * * * * * * ]
 Wow, much faster! Currently using 30 for max requests. Why isn't this enabled by default? Is this a security risk?
Offline Profile Quote Post Goto Top
 
alamir Apr 30 2005, 04:46 AM Post #20
Member Avatar
Electricity is just Organized Lightning.
[ * * * * ]
SkItZo
April 29, 2005 05:49 AM
I made it 150000000 for network.http.pipelining.maxrequests is that safe for me to use? Will it crash any of the websites I'm viewing? haha

I may be wrong about this, but I'm pretty sure it would have the opposite effect and allow a site to be able to crash your browser rather than your browser be able to crash it's site.
Especially if you're downloading a forum's thread that has 150000000 posts of huge flash animations on a single page :P .
Offline Profile Quote Post Goto Top
 
Nemesis Apr 30 2005, 10:02 AM Post #21
+o0 1337 |=0|- j00
[ * * * * ]
 well seth i didnt exactly mean bandwidth, but you will slow everyone else down who is viewing your site.

I talked to one of my friends about this. He does not recommend this.


Also, does anyone know if this will work ONLY for Firefox or will it also work for MOZILLA SUITE?
Offline Profile Quote Post Goto Top
 
Gornakle Apr 30 2005, 10:46 AM Post #22
Member
[ * * * * * ]
ASDF123
April 30, 2005 03:02 PM
Also, does anyone know if this will work ONLY for Firefox or will it also work for MOZILLA SUITE?

It should work for both. Just check if the preference is shown in about:config. :)
Offline Profile Quote Post Goto Top
 
Nemesis May 2 2005, 08:04 PM Post #23
+o0 1337 |=0|- j00
[ * * * * ]
funnyguy263
April 3, 2005 11:28 PM
If your using windows (most people do) and your running IE (which most people do), then go download firefox here: http://www.mozilla.org/products/firefox/

Now for those of you who do have firefox, this will make it run a lot faster:

If you have DSL/cable or anything higher then 56K, then you'll notice a big diffrence.

1.Type "about:config" into the address 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 will make several at once, which really speeds up page loading.

2. Alter the entries as follows:

Set "network.http.pipelining" to "true"

Set "network.http.proxy.pipelining" to "true"

Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

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.

If you're using a broadband connection you'll load pages MUCH faster now!

Hope it worked, well it should.

I told quite a few people about this and they had the same problem as me.


When we opened a page with LOTS of images (such as Microsoft ClipArt online), the browser could not load all the images. (only loaded a few of them)

The parts I have bolded in your post need to be set as False to prevent this problem. The speed is still the same even after this alteration, in addition to all the images loading without any problem.
Offline Profile Quote Post Goto Top
 
Captain Kam May 2 2005, 08:47 PM Post #24
Custom member title
[ * * * * * ]
 *turns pipelining off* Thanks ^_^
Offline Profile Quote Post Goto Top
 
Kenshin Himura May 2 2005, 10:18 PM Post #25
The random, ignorant, enlightened, IF fan.
[ * * * ]
 I thought that taking alot of requests from several people could "hiccup" a server.

Someone explain? =\
Offline Profile Quote Post Goto Top
 
Deleted User May 3 2005, 02:51 PM Post #26
Deleted User
ASDF123
May 2, 2005 05:04 PM
funnyguy263
April 3, 2005 11:28 PM
1.Type "about:config" into the address 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 will make several at once, which really speeds up page loading.

2. Alter the entries as follows:

Set "network.http.pipelining" to "true"

Set "network.http.proxy.pipelining" to "true"

Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

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.

If you're using a broadband connection you'll load pages MUCH faster now!

Hope it worked, well it should.

I told quite a few people about this and they had the same problem as me.


When we opened a page with LOTS of images (such as Microsoft ClipArt online), the browser could not load all the images. (only loaded a few of them)

The parts I have bolded in your post need to be set as False to prevent this problem. The speed is still the same even after this alteration, in addition to all the images loading without any problem.

If you set those to false, setting "network.http.pipelining.maxrequests" to 30 or anything else won't have any effect, will it?
So the only thing you'd actually be changing would be "nglayout.initialpaint.delay" :unsure:
Quote Post Goto Top
 
Zero Resistance-ZNS May 4 2005, 02:11 AM Post #27
eÜil Zero lÖrd™
[ * * * * ]
 More Requestd= less chance of a 400.

[Error 400: Bad Request]
Offline Profile Quote Post Goto Top
 
alamir May 4 2005, 11:30 AM Post #28
Member Avatar
Electricity is just Organized Lightning.
[ * * * * ]
 so this actually makes a site slower for everyone else?
Offline Profile Quote Post Goto Top
 
Jory May 4 2005, 03:24 PM Post #29
Member Avatar
Member
[ * * * * * * ]
 Well, it would make the server wanna send you the site 30 times.
So it might become slower for others.
(I think :unsure: )
Offline Profile Quote Post Goto Top
 
Zero Resistance-ZNS May 5 2005, 07:01 AM Post #30
eÜil Zero lÖrd™
[ * * * * ]
 YOu will send 30 requests for the site to load. actually somehow good, because some of them might fail. or bad if all of them manage not to come back empty handed.
Offline Profile Quote Post Goto Top
 
1 user reading this topic (1 Guest and 0 Anonymous)
Go to Next Page
« Previous Topic · Community Chat · Next Topic »
Add Reply
  • Pages:
  • 1
  • 2
  • 4