The Secrets of Firefox about:config

jcatcw writes "While Firefox is very customizable, many of its settings aren't in the Options. Each setting is named and stored as a string, integer, or Boolean in a file called prefs.js and accessed via about:config from the nav bar. Computerworld provides instructions on 20 tweaks for speeding up page loads, making tabs behave, reducing memory drain, and generally making the interface act the way you want it to. Customization also comes through the must-have FF extensions (but be sure to skip these)."

Comments

While it's nice..

[microbee]

Do not tune stuff that is hidden unless you know what you are doing.

Re:While it's nice..

[Anonymous Coward]

I particularly love the "pipelining" part. Send requests before getting valid acknowledgments from previous requests. ...

It's rude, annoying and breaks the rules/protocol.

From RFC 2616 (HTTP/1.1) section 8.1.1:

HTTP requests and responses can be pipelined on a connection. Pipelining allows a client to make multiple requests without waiting for each response, allowing a single TCP connection to be used much more efficiently, with much lower elapsed time.

Re:While it's nice..

[smittyoneeach]

http://subversion.tigris.org/faq.html#in-place-imp ort
Install Subversion, and use it on your config files.
Subversion: it's not just for projects anymore.

Re:While it's nice..

[hahafaha]

So if these options really make pages load faster, offer less memory drain, and even feed the dog, why aren't they a part of the settings to begin with?

Basically, because, although they may give more speed, they have drawbacks as well. Your question is like asking, ``If people can overclock their processors to so much faster, why isn't it overclocked by default?''

Tabs

[rustalot42684]

In Soviet Russia, Firefox keeps tabs on YOU!

link to one page article

[maj1k]

here

Foons!

[SimonTheSoundMan]

Well, a lot of these "tweaks" will have negative effects.

Example: nglayout.initialpaint.delay as 0. This will slow rendering of the page as it causes reflows. Fools.

official mozilla reference

[wizardforce]

http://kb.mozillazine.org/About:config_entries

Re:A bigger question

[jj110888]

Perhaps these tweaks are hidden because they are *not* worth doing?

The Art of Performance Tuning -- a Fable

[sillivalley]

A long time ago, when computers remembered using little donuts made of rust, I worked on on a mainframe computer system (CP/V) that supported batch, timesharing, realtime, the works. It had performance monitoring tools, and a large basketload of parameters for sys admins to twiddle.

One of our favorite parameters was SL:BB, documented as batch bias, an input to the process scheduler. When someone called or wrote to us saying they were having problems with performance tuning, we usually suggested they redo their tests varying the setting of SL:BB and let us know what happened. Try different values, 0, 1, 5, 20, 50, 100, things like that. Try it and get back to us.

And lo, they would go off and redo performance runs, and report back.

And we would collect their results and go and muse over them, usually over beer.

SL:BB told us a lot about the user, because SL:BB was a knob that wasn't connected to anything. Oh, the value was range-checked by the parameter setting tool, and dutifully stored in memory, and displayed on performance displays, but it didn't change system performance in any way at all.

That's not what the documentation said, but who believes documentation? We had plans for SL:BB, we just hadn't gotten around to writing the code yet.

So if the user reported that setting SL:BB to 25, but not 24 or 26 gave them incredibly better (or worse) results, we definitely factored that into our analysis.

Those that reported back that the setting of SL:BB didn't make a damn bit of difference, and there were some, we honored as brothers, took into our confidences, and shared beer with at the soonest opportunity. Their bug reports and feature requests received far more attention, for they had passed an important test.

And how many of these Firefox parameters are like SL:BB?

Re:Which option to make the Firehose work again?

[larry bagina]

set org.slashdot.dont_make_changes_on_the_live_server_ yes_im_talking_to_you_cmdrtaco=1

Hacking Firefox

[Dominare]

Gah. Why is it that these people insist on calling anything not found on the main options page "hacking"? As for the above questions - usually the reason things like that are 'hidden' is to stop people fiddling with them. A good example is the old 'coolbits' entry in the registry for nVidia cards - the overclocking functionality was there, but you had to do something non-standard to enable it. That way, the company's ass is covered if you melt your card; you can't pretend you enabled the options accidentally. Since Firefox is free and nobody is paying tech-support, I'm not sure why these things aren't available - but the fact of the matter is, anyone messing around with fundamental parameters should _not_ be the kind of person who lets random articles on the internet tell them what to change.

Re:A bigger question

[leathered]

Listen sonny, as a network admin I perform 'miracles' every day with a CLI and hidden options in config files. It impresses the PHBs, earns respect and keeps my salary up. And now you want to further trivialise my job with more GUI options. Oh for the good old days when all we had were ones and zeroes.