I stopped using it because they programmed it to only render the webpage once everything was loaded.
Can't see that this make the slightest bit of difference, certainly not that it trumps network latency, features and usability. I just did a few comparisons between Chrome and Firefox. Sod all difference.
still can't see any reason to switch to a chromium/blink based browser ... firefox (IceDragon version in my case) trumps them on functionality & there is no speed difference between them other than a fresh install 'boost' -- but that's the same for any browser!
perhaps if I used google docs etc I might have a different opinion BUT I'm not for this 'cloud' stuff beyond webmail!
I'm genuinely surprised to see a Firefox thread. Do people still use this browser?
... that would be the nubes, who decide to buy a new computer system for playing games on, and then simply use whatever is provided as standard, viz a viz IE.
Can't see that this make the slightest bit of difference, certainly not that it trumps network latency, features and usability. I just did a few comparisons between Chrome and Firefox. Sod all difference.
The last version of Firefox I used was quite noticeably slower in rendering webpages than Chrome was. This is the reason I switched to Chrome for. Unless they've went back to making Firefox render the webpage in chunks or whatever.
Edit: I'm talking about webpage items that aren't already in your browser's cache.
Indeed they do. I'm thinking of switching to Chrome though as I find FF a bit of a RAM hog these days. On my Macbook Air it's almost unusable.
Don't think Chrome is any more resource efficient, because of its multi-process implementation it actually uses more RAM than FF. Google seems to be sneakily creating an imitation of its Chrome OS via the browser.
I assure you the grass definitely aint greener on the other side, I am looking at 40% more ram usage.
Don't think Chrome is any more resource efficient, because of its multi-process implementation it actually uses more RAM than FF.
When I've looked I've observed that they use about the same amount of RAM as each other. (Possibly Opera pre-15+ has been the most memory efficient - I'm not sure - I do have it but use it rarely).
There seems to be a certain amount of confusion on this topic though. There are two issues.
1. High memory use.
2. Poor memory use, e.g., leaks, failure to release memory in a timely fashion or at all.
As far as Firefox is concerned it is designed to use more memory if it can to avoid having to use virtual memory. It does this for performance reasons. So memory use can by design be quite high depending on your system. This is not a problem unless it impacts other programs.
Then there is the separate issue of 2, which Firefox has traditionally suffered from, but I've noticed that it's been much better in this area from at least about v8/9 or even earlier.
Yeah, the programmers for Firefox must have changed the way it renders webpages back to the way it was before. Webpages are being displayed nice and fast now again. Back to Firefox it is then. I hate it when browsers only display webpages in one go. I'd rather they did it bits at a time, as quick as they can.
I hated the new download setup in the new Firefox,heres how to revert to the old download style.
Firefox reset download manager
Here's how to bring back the old standalone download manager:
1. Open a new tab.
2. Type about:config, then press Enter.
3. Paste the following into the search field: browser............download.useToolkitUI
4. Under the Value field, right-click false and then click Toggle. That should set the Value to "true."
5. Restart Firefox.
Don't think Chrome is any more resource efficient, because of its multi-process implementation it actually uses more RAM than FF. Google seems to be sneakily creating an imitation of its Chrome OS via the browser.
I assure you the grass definitely aint greener on the other side, I am looking at 40% more ram usage.
open fire fox and type in address bar
"about:config" then press enter
then it will show little warning ,click on
i will be careful
right click anywhere the page then
click on new -->string then a window will apper write in this window
"nglayout.initial.paint " then ok then put its value 00
third
right click anywhere the page then
click on new -->string then a window will apper write in this window
"content.notify.delay" then ok then put its value 00
Step_3: In the filter bar below the address bar type network.http.
Step_4: Double-click on "network.http.pipelining" to change the setting from false to true.
Step_5: Double-click on "network.http.proxy.pipelining" to change the value from false to true.
Step_6: Double-click on "network.http.pipelining.maxrequests" and change the number to "30". This means it will make 30 requests at once.
(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.)
Step_7: Several lines above network.http.proxy.pipelining you’ll see
"network.http.max-persistant-connections-per-proxy" and
"network.http.max-persistant-connections-per-server".
Double-click each line and change the value to "8".
Step_8: Two lines up locate and double-click on "network.http.max-connections" and set the value to "48".
Step_9: Now right-click (control-click on a Mac) anywhere in the configuration (the area where you’ve been making the changes). Select "New" then "Integer".
Step_10: When prompted, copy and paste or type the following into the field provided: nglayout.initialpaint.delay.
Step_11: When prompted to add a value, enter the number "0". This value is the amount of time the browser waits before it acts on information it recieves.
Step_12: Close all windows and tabs. The changes will take effect when you restart Firefox
These changes allow Firefox to make multiple server connections and will speed up page downloads for better, more efficient use of your broadband connection. If you're using a broadband connection you'll load pages MUCH faster now...
Reply With Quote
Comments
Dunno what's new mind.
5 seconds is hardly all week, perhaps it's your PC?
I stopped using it because they programmed it to only render the webpage once everything was loaded.
No such problem for me even with 20+ extensions.
Can't see that this make the slightest bit of difference, certainly not that it trumps network latency, features and usability. I just did a few comparisons between Chrome and Firefox. Sod all difference.
perhaps if I used google docs etc I might have a different opinion BUT I'm not for this 'cloud' stuff beyond webmail!
Firefox was awful when I last used it on OSX (almost 1 year ago now), memory usage used to just creep up and up.
The only difference I have noticed is my homepage now uses Bing rather than Google. I prefer Bing :eek: , so I like this change.
I find Windows 8 to be okay. Some others might just not have taken to it.
The last version of Firefox I used was quite noticeably slower in rendering webpages than Chrome was. This is the reason I switched to Chrome for. Unless they've went back to making Firefox render the webpage in chunks or whatever.
Edit: I'm talking about webpage items that aren't already in your browser's cache.
Don't think Chrome is any more resource efficient, because of its multi-process implementation it actually uses more RAM than FF. Google seems to be sneakily creating an imitation of its Chrome OS via the browser.
I assure you the grass definitely aint greener on the other side, I am looking at 40% more ram usage.
When I've looked I've observed that they use about the same amount of RAM as each other. (Possibly Opera pre-15+ has been the most memory efficient - I'm not sure - I do have it but use it rarely).
There seems to be a certain amount of confusion on this topic though. There are two issues.
1. High memory use.
2. Poor memory use, e.g., leaks, failure to release memory in a timely fashion or at all.
As far as Firefox is concerned it is designed to use more memory if it can to avoid having to use virtual memory. It does this for performance reasons. So memory use can by design be quite high depending on your system. This is not a problem unless it impacts other programs.
Then there is the separate issue of 2, which Firefox has traditionally suffered from, but I've noticed that it's been much better in this area from at least about v8/9 or even earlier.
Its Chrome by all accounts and so are a couple of others I tried.
Firefox reset download manager
Here's how to bring back the old standalone download manager:
1. Open a new tab.
2. Type about:config, then press Enter.
3. Paste the following into the search field: browser............download.useToolkitUI
4. Under the Value field, right-click false and then click Toggle. That should set the Value to "true."
5. Restart Firefox.
Many thanks for the tip works a charm as i hated the new behaviour
So what Mac browser isn't a RAM hog then?
Two seconds here! Something ain't right at your end, perhaps. :cool:
Is that after the computer/laptop being switched off or coming out of sleep?
open fire fox and type in address bar
"about:config" then press enter
then it will show little warning ,click on
i will be careful
right click anywhere the page then
click on new -->string then a window will apper write in this window
"nglayout.initial.paint " then ok then put its value 00
third
right click anywhere the page then
click on new -->string then a window will apper write in this window
"content.notify.delay" then ok then put its value 00
Step_3: In the filter bar below the address bar type network.http.
Step_4: Double-click on "network.http.pipelining" to change the setting from false to true.
Step_5: Double-click on "network.http.proxy.pipelining" to change the value from false to true.
Step_6: Double-click on "network.http.pipelining.maxrequests" and change the number to "30". This means it will make 30 requests at once.
(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.)
Step_7: Several lines above network.http.proxy.pipelining you’ll see
"network.http.max-persistant-connections-per-proxy" and
"network.http.max-persistant-connections-per-server".
Double-click each line and change the value to "8".
Step_8: Two lines up locate and double-click on "network.http.max-connections" and set the value to "48".
Step_9: Now right-click (control-click on a Mac) anywhere in the configuration (the area where you’ve been making the changes). Select "New" then "Integer".
Step_10: When prompted, copy and paste or type the following into the field provided: nglayout.initialpaint.delay.
Step_11: When prompted to add a value, enter the number "0". This value is the amount of time the browser waits before it acts on information it recieves.
Step_12: Close all windows and tabs. The changes will take effect when you restart Firefox
These changes allow Firefox to make multiple server connections and will speed up page downloads for better, more efficient use of your broadband connection. If you're using a broadband connection you'll load pages MUCH faster now...
Reply With Quote