Kako pohitriti FireFox

Ker sem opazil da zelo veliko ljudi uporablja Mozillo Firefox sem napisal vodič kako jo pohitriti:

1: vpiši "about:config" v URL polje, polje kjer vpišeš URL kašnega page-a,
2: nastavi vrednost "network.http.pipelining" na "true",
3: nastavi vrednost "network.http.pipelining.maxrequests" na "100",
4: nastavi vrednost "network.http.proxy.pipelining" na "true",

Pete možnosti ni na spisku in jo morate ustvariti tako da pritisnete desni klik kjerkoli v Mozilli (seveda se še nahajamo v about:config) ter date New (Novo) in nato Integer ter potem napišete najprej nglayout.initialpaint.delay
potem date OK in nato vpišete vrednost 0.
Potem se Mozillo zaprete in nazaj odprete in strani bi se morale odpirati hitreje.

Dela preverjeno pri meni.

kopirano iz druge spletne strani...

pri meni je vsekakor vidna razlika, hitreje se mi odpirajo strani in zavihki, tako da nevem.....Morda imaš dobro linijo in imaš že tako hiter internet, da ni potreben izboljšave oz. že deluje na t.i. maximunu...Jaz imam linijo 1mb in mi pomaga..

Ah staro, že blo!
Da ponovimo, se pa pozna pri linijah nekje do 1/1 Mbit/s, vsaj kar se tiče mojih iskušanj.

Za vse tiste, ki uporabljate Firefox je tukaj nekaj sprememb, ki pohitrijo vaš Firefox. Meni se kar lepo pozna.

1. Napišite "about:config" v prostor kamor pišete naslove strani.
2. Poiščite network.http.pipelining in ga nastavite na "true".
3. Poiščite network.http.pipelining.maxrequests in ga nastavite na "100".
4. Poiščite network.http.proxy.pipelining in ga nastavite na "true"
5. Poiščite nglayout.initialpaint.delay in ga nastavite na "0"

Če kateri od teh predmetov ne obstaja, kliknite z desnim gumbom na vašem mišaku in izberite "new".

new -> glede na to kateri predmet vam manjka izberite:

boolean -> če ima predmet za nastavljanje true/false
integet -> če ima predmet za nastavljanje številke
_______________________________________________________________________________
še je tega:

Performance Settings

One of the limitations of pretty much all computer applications is the need to target for a general audience because of the wide array of computer components and varied network infrastructure. This is where tweaking comes in. Firefox by default is aimed at a general audience too and hopefully we can tune it more to the needs of the individual. The majority of the information comes from this excellent thread over at the MozillaZine Forum. The first post in particular goes through in great detail what each of the settings do. The thread however gets fairly long and convoluted and we attempt to summarize the contents of this thread along with a couple other sources into something that is easier to digest. As with the settings on the previous page, the contents are copied into the user.js file. We do not go into major detail about the setting as the thread goes into detailed explanations of what the settings mean in the first post. Instead, the configurations are culled from the thread of what people have reported to have worked for them along with some modifications on our end.

Quick and Dirty Settings

user_pref("network.http.pipelining", true);
user_pref("network.http.pipelining.firstrequest", true);
user_pref("network.http.pipelining.maxrequests", 8);
user_pref("nglayout.initialpaint.delay", 0);

These were some settings I ran across sometime ago. Pipelining does multiple data requests at once and should speed things up. I believe IE did this before and this was partially attributable to the speed advantage that IE had over older versions of Mozilla/Netscape. Initial Paint Delay actually slows down the rendering of the ENTIRE page but since users tend to start reading before the entire page is rendered, setting this to a low value gives the impression that the page loads faster.

The following configurations are based off of recommendations off of the Mozillazine thread with some editing on points that I do not agree with
Common to all configurations

These are the settings that seem to be common to all configuration files regardless of connection speed or computer speed with a couple of additions - plugin paths can be found with about:plugins and the bookmark menu delay is turned off.

user_pref("network.http.pipelining", true);
user_pref("network.http.proxy.pipelining", true);
user_pref("network.http.pipelining.maxrequests", 8);
user_pref("content.notify.backoffcount", 5);
user_pref("plugin.expose_full_path", true);
user_pref("ui.submenuDelay", 0);

Fast Computer Fast Connection

user_pref("content.interrupt.parsing", true);
user_pref("content.max.tokenizing.time", 2250000);
user_pref("content.notify.interval", 750000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 750000);
user_pref("nglayout.initialpaint.delay", 0);
user_pref("network.http.max-connections", 48);
user_pref("network.http.max-connections-per-server", 16);
user_pref("network.http.max-persistent-connections-per-proxy", 16);
user_pref("network.http.max-persistent-connections-per-server", 8);
user_pref("browser.cache.memory.capacity", 65536);

A couple settings of note - Firefox is allocated 4096 KB of memory by default and in this configuration we give it roughly 65MB as denoted by the last line. This can be changed according to what is used.

Fast Computer, Slower Connection

This configuration is more suited to people without ultra fast connections. We are not talking about dial up connections but slower DSL / Cable connections.

user_pref("content.max.tokenizing.time", 2250000);
user_pref("content.notify.interval", 750000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 750000);
user_pref("network.http.max-connections", 48);
user_pref("network.http.max-connections-per-server", 16);
user_pref("network.http.max-persistent-connections-per-proxy", 16);
user_pref("network.http.max-persistent-connections-per-server", 8);
user_pref("nglayout.initialpaint.delay", 0);
user_pref("browser.cache.memory.capacity", 65536);

Fast Computer, Slow Connection
user_pref("browser.xul.error_pages.enabled", true);
user_pref("content.interrupt.parsing", true);
user_pref("content.max.tokenizing.time", 3000000);
user_pref("content.maxtextrun", 8191);
user_pref("content.notify.interval", 750000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 750000);
user_pref("network.http.max-connections", 32);
user_pref("network.http.max-connections-per-server", 8);
user_pref("network.http.max-persistent-connections-per-proxy", 8);
user_pref("network.http.max-persistent-connections-per-server", 4);
user_pref("nglayout.initialpaint.delay", 0);
user_pref("browser.cache.memory.capacity", 65536);

Slow Computer, Fast Connection
user_pref("content.max.tokenizing.time", 3000000);
user_pref("content.notify.backoffcount", 5);
user_pref("content.notify.interval", 1000000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 1000000);
user_pref("content.maxtextrun", 4095);
user_pref("nglayout.initialpaint.delay", 1000);
user_pref("network.http.max-connections", 48);
user_pref("network.http.max-connections-per-server", 16);
user_pref("network.http.max-persistent-connections-per-proxy", 16);
user_pref("network.http.max-persistent-connections-per-server", 8);
user_pref("dom.disable_window_status_change", true);

One of the changes made for this particular configuration is the final line where the status bar is disabled for changing web pages to save processor time.

Slow Computer, Slow Connection

We have entered the doldrums of the dial-up user

user_pref("content.max.tokenizing.time", 2250000);
user_pref("content.notify.interval", 750000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 750000);
user_pref("nglayout.initialpaint.delay", 750);
user_pref("network.http.max-connections", 32);
user_pref("network.http.max-connections-per-server", 8);
user_pref("network.http.max-persistent-connections-per-proxy", 8);
user_pref("network.http.max-persistent-connections-per-server", 4);
user_pref("dom.disable_window_status_change", true);

Some of the options we chose not to include as opposed to suggestions on the Mozillazine threads included the suggestion of catching SSL pages. Regardless of computer speed, one of the common trends is that pipelining is a good thing. Those with faster computers and gobs of memory may want to up the amount of memory available to Firefox while those with slower computers can still increase the default 4MB to something higher. This was not done in our configuration files however. Powerusers are also welcome to disable the status bar to eek out that extra CPU cycle or two.

Mislim, da je sedaj okoli tega že preveč povedano!

lp

ant
Zate je rešitev program cFosSpeed
Glede delovanja programa pa si preberi info.

lp

Zakaj komplicirate in ne preprosto potegnete dol dodatka imenovanga FasterFox?

se "patch" za SP3

pa kaj je fora tega patcha? kaj sploh naredi in ali je to nujno, saj že imam sp2.

Microsoft Windows XP Service Pack 2 introduces a limited TCP connection, which is set to a maximum of 10 (the previous limit was over 65,000). This is “supposed” to protect the host PC from connecting to a high amount of random IP numbers.
Since some malicious worms could spread by connecting to a high amount of random IP numbers, Microsoft, in their infinite wisdom, introduced a patch in SP2 to limit the TCP connection to 10.
Regrettably, this also slows down application that relies on many connections (such as the BitTorrent client). This limit has the potential to cause slowdowns in certain situations.
An unofficial patch will modify the locked tcpip.sys and let you set the limit to whatever you wish.

some “windows updates” revert your tweaked tcp connections back to 10. So it’s wise to check this every now and then. You can check this by going to (in windows xp) Start > Control Panel > Administrative Tools > Event Viewer > System… Look for event 4226 (sort by event)