Firefox 2.0 final is out

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

BD2003

Lifer
Oct 9, 1999
16,815
1
81
Originally posted by: ScottSwingleComputers
Originally posted by: BD2003
I don't understand how you guys can use such a slow browser.

Extensions are cool and all, but I just can't deal with how slow it is and how much memory it uses. It's too bad they don't make a plugin that lets you use the opera engine to render the page in FF, like they do for IE.

SLOW!?!?!? In my experience, FF is MUCH faster. Pages load quicker, the program itself opens faster, etc.

FF is faster in some ways than IE, but only by a bit.

Opera on the other hand, is stupendously faster than both.

I've tried several times to move from opera to FF because extensions do kick major ass. And after I've used FF for a while, Ill get used to its slowness. Then I'll fire up opera, and realize how much faster it is, and I just can't go back.

I'm not talking about just loading pages faster. It's just faster, more responsive in every way. I could go back or forward five pages in in the time it takes FF to go back one. Firefox feels like it has molasses embedded in it's code.
 

ultravox

Elite Member
Oct 9, 1999
2,072
12
81
Here's something for broadband people that will really speed Firefox up:

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 35.
This means it will make 35 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!
 

tami

Lifer
Nov 14, 2004
11,588
3
81
is anyone able to press the forward slash (/) button to get the Find bar or does this not work?

i don't think that "Find" is working at all for me.

:(
 

Mo0o

Lifer
Jul 31, 2001
24,227
3
76
is there a way to integrate thunderbird into FF? Thats one of the reasons I really like Opera, it's built in mail browser program.
 

Dean

Platinum Member
Oct 10, 1999
2,757
0
76
Will download it when I get home. I hope Noia has a Firefox 2.0 compatible theme now. I am so used to that theme that Firefox looks bland without it.
 

Shawn

Lifer
Apr 20, 2003
32,236
53
91
Originally posted by: tami
is anyone able to press the forward slash (/) button to get the Find bar or does this not work?

i don't think that "Find" is working at all for me.

:(

works fine for me. neat trick.
 

tami

Lifer
Nov 14, 2004
11,588
3
81
Originally posted by: Shawn
Originally posted by: tami
is anyone able to press the forward slash (/) button to get the Find bar or does this not work?

i don't think that "Find" is working at all for me.

:(

works fine for me. neat trick.


why thank you!

but this sucks... i lost all my bookmarks too... and i had a ton

wtf.
 

Aves

Lifer
Feb 7, 2001
12,232
30
101
Originally posted by: tami
is anyone able to press the forward slash (/) button to get the Find bar or does this not work?

It works for me.

:confused:
 

Shawn

Lifer
Apr 20, 2003
32,236
53
91
Originally posted by: ultravox
Here's something for broadband people that will really speed Firefox up:

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 35.
This means it will make 35 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!

works great. thanks.
 

Shawn

Lifer
Apr 20, 2003
32,236
53
91
Originally posted by: tami
Originally posted by: Shawn
Originally posted by: tami
is anyone able to press the forward slash (/) button to get the Find bar or does this not work?

i don't think that "Find" is working at all for me.

:(

works fine for me. neat trick.


why thank you!

but this sucks... i lost all my bookmarks too... and i had a ton

wtf.

sounds like your install got corrupt.

 

MrChad

Lifer
Aug 22, 2001
13,507
3
81
Originally posted by: Mo0o
is there a way to integrate thunderbird into FF? Thats one of the reasons I really like Opera, it's built in mail browser program.

Have you tried Seamonkey?
 

WildHorse

Diamond Member
Jun 29, 2003
5,006
0
0
Originally posted by: keeleysam
Originally posted by: thescreensavers
Its RC3 not final.... look at properties the version is the same as rc3 which is 4.42.0.0

RC3 was accepted as final.

Read before you speak.
Are you sure of that?

Can you please give a link to someplace where we can verify RC3 was accepted as final?
 

thescreensavers

Diamond Member
Aug 3, 2005
9,916
2
81
Originally posted by: ultravox
Here's something for broadband people that will really speed Firefox up:

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 35.
This means it will make 35 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!

were did you get this?
 

Jeffwo

Platinum Member
Mar 2, 2001
2,759
0
76
Originally posted by: Pshawn5
Did they fix the problem with flash player? I've tried the suggestions on the Mozilla knowledge base to fix the problem, but yet whenever i go to a flash player website such as youtube, Firefox crashes. it's becoming a annoying problem.

Same problem here. I never got Flash to work with FF.

:(
Jeff

 

TraumaRN

Diamond Member
Jun 5, 2005
6,893
63
91
Originally posted by: thescreensavers
Originally posted by: ultravox
Here's something for broadband people that will really speed Firefox up:

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 35.
This means it will make 35 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!

were did you get this?

Holy smokes did my FF just speed up :thumbsup:
 

tami

Lifer
Nov 14, 2004
11,588
3
81
Originally posted by: thescreensavers
Originally posted by: ultravox
Here's something for broadband people that will really speed Firefox up:

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 35.
This means it will make 35 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!

were did you get this?

probably at one of the eleventy billion sites that already display that information. it's a useful tweak for 1.x also.

http://bijitsu.multiply.com/links/item/20
 

Shawn

Lifer
Apr 20, 2003
32,236
53
91
Originally posted by: Jeffwo
Originally posted by: Pshawn5
Did they fix the problem with flash player? I've tried the suggestions on the Mozilla knowledge base to fix the problem, but yet whenever i go to a flash player website such as youtube, Firefox crashes. it's becoming a annoying problem.

Same problem here. I never got Flash to work with FF.

:(
Jeff

delete any existing flash plugin then download the latest version. flash has always worked fine for me.
 

BD2003

Lifer
Oct 9, 1999
16,815
1
81
Originally posted by: ultravox
Here's something for broadband people that will really speed Firefox up:

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 35.
This means it will make 35 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!

It's easier to just download the extension "fasterfox", which does all of the exact same things, just with a nice UI and all, and makes it easier to test the effects of the speedups.

The network ones speed up the rate of download, but not the rate of rendering, or cpu/mem usage, unfortunately. Pipelining is generally good, although a rare website has a problem with it, which is why it's off by default. I wouldn't recommend putting the max requests as high as 35- you might be pulling in 35 streams at once (images etc), but that will only speed you up if you are REALLY bottlenecked. Leave it at 8-16 or less, unless you have a ton of bandwidth, and really fast cpu/memory.

You can only download as fast as you have bandwidth for, you can either download 30 things in 5 seconds, twice. Or download all 60 at once, over 10 seconds. It's not going to be much faster in the end past a certain point of diminishing returns, and will eventually become counter-productive.

I definitely do not recommend to set the inital paint to 0. The setting determines how long to wait before rendering the new page, and it's set to wait for a very good reason. If you set it to 0, it will repaint before ANY data has come in, therefore every single click will be met with a white screen, before it starts loading. That alone annoys me. Secondly, the primary reason it waits is so that it can get enough data that it can render the page without having to constantly reformat it as new tables, multiple large images, etc come in, which is cpu intensive, and FF does not handle this particularly well at all. Especially if it has to reformat the page a million times because it's starting from a blank canvas. You can barely scroll around while its doing so, on a large complicated page. FF seems more intent to get all the data loaded and formatted before you can smoothly use it, at the expense of responsiveness, which probably has a lot to do with why the inital delay is so high in the first place.

If you set it to 0, you might perceive it being faster because it blinks to white so fast, and you can see it all coming in. But if you set it to a more reasonable value, it'll have enough data, that it'll have less work to do when it eventually does begin to render, speeding you up. Depending on your bandwidth and CPU, I'd set it from a minimum 100 (1/10th of a sec, still very fast). I usually go for 200-250ms. The default is set at 1000ms, which is far too safe in my opinion, but is a good number for slower computers.

Best thing to do is to get fasterfox, which has a built in timer, and an easy way to clear the cache, so you can see for yourself the effects the tweaks has.

And all that being said, Opera is still at least twice as fast. :p In fact, FF 2.0 is probably the slowest one they've put out! See here:

http://www.howtocreate.co.uk/browserSpeed.html

The latest Opera starts up several times faster, renders and runs scripts 2-3 times faster, loads images multiple images at a time 50% faster, and goes back/forward through history 600% faster.

But extensions still kick ass. :p Can't have it all. :(
 

GeneValgene

Diamond Member
Sep 18, 2002
3,884
0
76
Originally posted by: BD2003
Originally posted by: ScottSwingleComputers
Originally posted by: BD2003
I don't understand how you guys can use such a slow browser.

Extensions are cool and all, but I just can't deal with how slow it is and how much memory it uses. It's too bad they don't make a plugin that lets you use the opera engine to render the page in FF, like they do for IE.

SLOW!?!?!? In my experience, FF is MUCH faster. Pages load quicker, the program itself opens faster, etc.

FF is faster in some ways than IE, but only by a bit.

Opera on the other hand, is stupendously faster than both.

I've tried several times to move from opera to FF because extensions do kick major ass. And after I've used FF for a while, Ill get used to its slowness. Then I'll fire up opera, and realize how much faster it is, and I just can't go back.

I'm not talking about just loading pages faster. It's just faster, more responsive in every way. I could go back or forward five pages in in the time it takes FF to go back one. Firefox feels like it has molasses embedded in it's code.

i agree...you don't realize it until you use opera how fast...even on slow machines, opera is blazing

 

Platypus

Lifer
Apr 26, 2001
31,046
321
136
You shouldn't have to break http standards to speed up a browser nor should it eat up 800MB of ram. I hate FF but there's nothing else as customizable out there right now.
 
Jul 12, 2001
10,142
2
0
so besides the spell check, what makes this one better?

I dont like how they got rid of the [x] on the far right of the tab bar to close the current tab....i believe thats where it was, at least thats where my hand naturally went...now they have a drop down of the current tabs there
 

secretanchitman

Diamond Member
Apr 11, 2001
9,352
23
91
Originally posted by: BD2003
Originally posted by: ultravox
Here's something for broadband people that will really speed Firefox up:

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 35.
This means it will make 35 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!

It's easier to just download the extension "fasterfox", which does all of the exact same things, just with a nice UI and all, and makes it easier to test the effects of the speedups.

The network ones speed up the rate of download, but not the rate of rendering, or cpu/mem usage, unfortunately. Pipelining is generally good, although a rare website has a problem with it, which is why it's off by default. I wouldn't recommend putting the max requests as high as 35- you might be pulling in 35 streams at once (images etc), but that will only speed you up if you are REALLY bottlenecked. Leave it at 8-16 or less, unless you have a ton of bandwidth, and really fast cpu/memory.

You can only download as fast as you have bandwidth for, you can either download 30 things in 5 seconds, twice. Or download all 60 at once, over 10 seconds. It's not going to be much faster in the end past a certain point of diminishing returns, and will eventually become counter-productive.

I definitely do not recommend to set the inital paint to 0. The setting determines how long to wait before rendering the new page, and it's set to wait for a very good reason. If you set it to 0, it will repaint before ANY data has come in, therefore every single click will be met with a white screen, before it starts loading. That alone annoys me. Secondly, the primary reason it waits is so that it can get enough data that it can render the page without having to constantly reformat it as new tables, multiple large images, etc come in, which is cpu intensive, and FF does not handle this particularly well at all. Especially if it has to reformat the page a million times because it's starting from a blank canvas. You can barely scroll around while its doing so, on a large complicated page. FF seems more intent to get all the data loaded and formatted before you can smoothly use it, at the expense of responsiveness, which probably has a lot to do with why the inital delay is so high in the first place.

If you set it to 0, you might perceive it being faster because it blinks to white so fast, and you can see it all coming in. But if you set it to a more reasonable value, it'll have enough data, that it'll have less work to do when it eventually does begin to render, speeding you up. Depending on your bandwidth and CPU, I'd set it from a minimum 100 (1/10th of a sec, still very fast). I usually go for 200-250ms. The default is set at 1000ms, which is far too safe in my opinion, but is a good number for slower computers.

Best thing to do is to get fasterfox, which has a built in timer, and an easy way to clear the cache, so you can see for yourself the effects the tweaks has.

And all that being said, Opera is still at least twice as fast. :p In fact, FF 2.0 is probably the slowest one they've put out! See here:

http://www.howtocreate.co.uk/browserSpeed.html

The latest Opera starts up several times faster, renders and runs scripts 2-3 times faster, loads images multiple images at a time 50% faster, and goes back/forward through history 600% faster.

But extensions still kick ass. :p Can't have it all. :(

i was going to suggest fasterfox as well. im pretty sure even though its incompatible with ff2.0, it runs fine.