zOMG at its best! (Optimization & performance enhancement)

How well did this tutorial help you?

Yes - Amazing difference, this ought to be a sticky	48.0%	[ 1088 ]
Yes - Moderate difference	24.4%	[ 554 ]
Yes - Minor difference	12.6%	[ 285 ]
No - I was unable to notice a significant change	15.0%	[ 340 ]
Total Votes:			[ 2267 ]

[acyushi]

Thank you for this! I'm already using AdBloock, but I'm restarting FireFox now to see if I notice a difference with the pipeline stuff. surprised

[GamesTesterJan]

fatcheehcs

I tried out one of Okatantoon's (sp?) suggestions, the second one. That one made a significant difference for me, so THANKS A LOT for posting it!!! heart heart

Now if only zOMG would load... stare

It does look like a great pipelining tutorial, I'll give it a test out when I have the time and probably add it to the main tutorial. I believe some pipelining techniques work better for others perhaps even having two would be nice.

Miss. M

Thank you for this! I'm already using AdBloock, but I'm restarting FireFox now to see if I notice a difference with the pipeline stuff. surprised

Glad to hear it, continue with the rest and in game options and hopefully you will be enjoying zOMG more then ever.

[Katantoon]

Hey I'm back. I found the tweak I'm currently using in my firefox. It won't make a miracle but it helped my firefox ran faster. It's a little but long you don't need to download anything :3.

Regards to my friend who is not on gaia for this. :3

ANOTHER TWEAKING


1. Type about:config in the address bar and then press Enter.


2. In the filter search bar type network.http.pipelining. Be sure the value field is set
true,if not double-click to set true.
HTTP is the application-layer protocol that most web pages are transferred with. In
HTTP 1.1, multiple requests can be sent before any responses are received. This is known
as pipelining. Pipelining reduces page loading times, but not all servers support it.


3. Go back to the filter search bar and type network.http.pipelining.maxrequests.
Double-click this option and set its value to 8.


4. In the filter search bar and type network.http.proxy.pipelining. Once opened doubleclick
on it and set it to true.


5. In IPv6-capable DNS servers, an IPv4 address may be returned when an IPv6 address
is requested. It is possible for Mozilla to recover from this misinformation, but a
significant delay is introduced.
Type network.dns.disableIPv6 in the filter search bar and set this option to true by
double clicking on it.


6. CONTENT INTERRUPT PARSING
This preference controls if the application will interrupt parsing a page to respond to UI
events. It does not exist by default.
Right-click (Apple users ctrl-click) anywhere in the about:config window, select New
and then Boolean from the pop-up menu. Then:
A. Enter content.interrupt.parsing in the New boolean value pop-up window and click
OK
B. When prompted to choose the value for the new boolean, select true and click OK.


7. Rather than wait until a page has completely downloaded to display it to the user,
Mozilla applications will regularly render what has been received to that point. This
option controls the maximum amount of time the application will be unresponsive while
rendering pages.
Right-click (Apple users ctrl-click) anywhere in the about:config window, select New
and then Integer from the pop-up menu.
A. Enter content.max.tokenizing.time in the New integer value pop-up window and
click OK
B. You will be prompted to enter a value. Enter 2250000 and click OK.


8. CONTENT NOTIFY INTERVAL
This option sets the minimum amount of time to wait between reflows. Right-click
(Apple users ctrl-click) anywhere in the about:config window, select New and then
Integer from the pop-up menu.
A. Type content.notify.interval in the New integer value pop-up window and click OK.
B. You will be prompted to enter a value. Enter 750000 and click OK.


9. CONTENT NOTIFY ONTIMER
A. This option sets if to reflow pages at an interval any higher than that specified by
content.notify.interval. Right-click (Apple users ctrl-click) anywhere in the
about:config window and select New and then Boolean from the pop-up menu.
B. Type content.notify.ontimer in the New boolean value pop-up window and click OK.
C. You will be prompted to choose the value for the new boolean. Select true and click
OK.


10. Notify Backoffcount
This option controls the maximum number of times the content will do timer-based
reflows. After this number has been reached, the page will only reflow once it is finished
downloading. Right-click (Apple users ctrl-click) anywhere in the about:config window
and select New and then Integer from the pop-up menu.
A. Enter content.notify.backoffcount in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 5 and click OK.


11. CONTENT SWITCH THRESHOLD
You can interact with a loading page when content.interrupt.parsing is set to true.
When a page is loading, the application has two modes: a high frequency interrupt mode
and a low frequency interrupt mode. The first one interrupts the parser more frequently to
allow for greater UI responsiveness during page load.
The low frequency interrupt mode interrupts the parser less frequently to allow for
quicker page load. The application enters high frequency interrupt mode when you move
the mouse or type on the keyboard and switch back to low frequency mode when you had
no activity for a certain amount of time. This preference controls that amount of time.
Right-click (Apple users ctrl-click) anywhere in the about:config window and select
New and then Integer from the pop-up menu.
A. Enter content.switch.threshold in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 750000 and click OK.


12. NGLAYOUT INITIALPAINT DELAY
Mozilla applications render web pages incrementally, they display what’s been received
of a page before the entire page has been downloaded. Since the start of a web page
normally doesn’t have much useful information to display, Mozilla applications will wait
a short interval before first rendering a page. This preference controls that interval. Rightclick
(Apple users ctrl-click) anywhere in the about:config window and select New and
then Integer from the pop-up menu.
A. Enter nglayout.initialpaint.delay in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 0 and click OK.


13. Just restart your firefox after finishing all the procedures.

[Silly RiRi]

Thank you so much for all this! My Firefox is working so much smoother now whee

[GamesTesterJan]

O_OkatantoonO_O

Hey I'm back. I found the tweak I'm currently using in my firefox. It won't make a miracle but it helped my firefox ran faster. It's a little but long you don't need to download anything :3.

Regards to my friend who is not on gaia for this. :3

ANOTHER TWEAKING


1. Type about:config in the address bar and then press Enter.


2. In the filter search bar type network.http.pipelining. Be sure the value field is set
true,if not double-click to set true.
HTTP is the application-layer protocol that most web pages are transferred with. In
HTTP 1.1, multiple requests can be sent before any responses are received. This is known
as pipelining. Pipelining reduces page loading times, but not all servers support it.


3. Go back to the filter search bar and type network.http.pipelining.maxrequests.
Double-click this option and set its value to 8.


4. In the filter search bar and type network.http.proxy.pipelining. Once opened doubleclick
on it and set it to true.


5. In IPv6-capable DNS servers, an IPv4 address may be returned when an IPv6 address
is requested. It is possible for Mozilla to recover from this misinformation, but a
significant delay is introduced.
Type network.dns.disableIPv6 in the filter search bar and set this option to true by
double clicking on it.


6. CONTENT INTERRUPT PARSING
This preference controls if the application will interrupt parsing a page to respond to UI
events. It does not exist by default.
Right-click (Apple users ctrl-click) anywhere in the about:config window, select New
and then Boolean from the pop-up menu. Then:
A. Enter content.interrupt.parsing in the New boolean value pop-up window and click
OK
B. When prompted to choose the value for the new boolean, select true and click OK.


7. Rather than wait until a page has completely downloaded to display it to the user,
Mozilla applications will regularly render what has been received to that point. This
option controls the maximum amount of time the application will be unresponsive while
rendering pages.
Right-click (Apple users ctrl-click) anywhere in the about:config window, select New
and then Integer from the pop-up menu.
A. Enter content.max.tokenizing.time in the New integer value pop-up window and
click OK
B. You will be prompted to enter a value. Enter 2250000 and click OK.


8. CONTENT NOTIFY INTERVAL
This option sets the minimum amount of time to wait between reflows. Right-click
(Apple users ctrl-click) anywhere in the about:config window, select New and then
Integer from the pop-up menu.
A. Type content.notify.interval in the New integer value pop-up window and click OK.
B. You will be prompted to enter a value. Enter 750000 and click OK.


9. CONTENT NOTIFY ONTIMER
A. This option sets if to reflow pages at an interval any higher than that specified by
content.notify.interval. Right-click (Apple users ctrl-click) anywhere in the
about:config window and select New and then Boolean from the pop-up menu.
B. Type content.notify.ontimer in the New boolean value pop-up window and click OK.
C. You will be prompted to choose the value for the new boolean. Select true and click
OK.


10. Notify Backoffcount
This option controls the maximum number of times the content will do timer-based
reflows. After this number has been reached, the page will only reflow once it is finished
downloading. Right-click (Apple users ctrl-click) anywhere in the about:config window
and select New and then Integer from the pop-up menu.
A. Enter content.notify.backoffcount in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 5 and click OK.


11. CONTENT SWITCH THRESHOLD
You can interact with a loading page when content.interrupt.parsing is set to true.
When a page is loading, the application has two modes: a high frequency interrupt mode
and a low frequency interrupt mode. The first one interrupts the parser more frequently to
allow for greater UI responsiveness during page load.
The low frequency interrupt mode interrupts the parser less frequently to allow for
quicker page load. The application enters high frequency interrupt mode when you move
the mouse or type on the keyboard and switch back to low frequency mode when you had
no activity for a certain amount of time. This preference controls that amount of time.
Right-click (Apple users ctrl-click) anywhere in the about:config window and select
New and then Integer from the pop-up menu.
A. Enter content.switch.threshold in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 750000 and click OK.


12. NGLAYOUT INITIALPAINT DELAY
Mozilla applications render web pages incrementally, they display what’s been received
of a page before the entire page has been downloaded. Since the start of a web page
normally doesn’t have much useful information to display, Mozilla applications will wait
a short interval before first rendering a page. This preference controls that interval. Rightclick
(Apple users ctrl-click) anywhere in the about:config window and select New and
then Integer from the pop-up menu.
A. Enter nglayout.initialpaint.delay in the New integer value pop-up window and click
OK.
B. You will be prompted to enter a value. Enter 0 and click OK.


13. Just restart your firefox after finishing all the procedures.

Ahhhh I've not even had the chance to full test the other one you submitted lol. Still this looks great, ideally what I am trying to do is make easy to follow and conflict free pipelining and anything else which will make zOMG play smoother and load quicker so it will need to have support for all the servers from Apache2 to what ever. Once I'm done I'll update and post my findings, I am in the middle of creating a new type "master pipelining" tutorial which I owe you some credit for submitting your alternative method.

[Katantoon]

Lol. The 2nd one I posted is the one I use now. :3 nod:

Hehe yeah, this thing can be not-so-user-friendly.

[Heen-san]

gametesterjan is my clan leader and i'll tell you he has been trying to get me to use firefox for a while now. im pretty avid about using IE though i will say ive been getting annoyed with gaia cause it didnt run fast like it used too after all these changes and advertisement. that and zomg would lag like crazy. finally decided to try his method only because he has everything step by step and i know he knows what hes talking about. after i did it though, DAMN! gaia was loading the market pages so fast i couldnt keep up with it and i didnt lag much anymore in zomg so i actually got to do something on there now. i will say i still use IE but for gaia and zomg, firefox is the way to go if you want to run better. cant wait til him and others find even more ways to make gaia and zomg run faster

[Really Kevin]

Eh...it's been running a little better. Good stuff though. I'll definitely keep checking back for updates. smile

[Caiel Iries]

This is wonderful. Thanks for sharing this with us. It has now made my Firefox faster and better. <3

Yay for less lag. HEE. xd

[Beast Henshin]

Holy crap! Awesome! it tooke me forever to figure out that you put the number for the integer after you type it in. That was my blond moment for the day (I'm glad I had it in private, lol)

[Secks Shae]

Leave it to the ZEL to have something like this biggrin

[PowderedVinegar]

when you explain the config for mozilla..... can you explain what this is actually doing. and how to undo it if we are unsatisfied

also, while i too prefer mozilla, there are some who find IE smoother. And some who like google Chrome.. the google chrome gave me GIM lag.

as for adblock: while it does work it makes me invisible even with the exception..... but i seem to have understood from that section that simply having it installed decreases lag. can you go into more details about your settings and exactly what u blocked? thank you~~~

[GamesTesterJan]

PowderedVinegar

when you explain the config for mozilla..... can you explain what this is actually doing. and how to undo it if we are unsatisfied

also, while i too prefer mozilla, there are some who find IE smoother. And some who like google Chrome.. the google chrome gave me GIM lag.

as for adblock: while it does work it makes me invisible even with the exception..... but i seem to have understood from that section that simply having it installed decreases lag. can you go into more details about your settings and exactly what u blocked? thank you~~~

I can go into a detailed tutorial but want it to be clear, concise and intuitive as often having a lot of information puts of a lot of users from trying or reading. I'll definitely consider making a indepth tutorial with an explanation till then if you find something is not working as you like you can reset the option or options to the default settings.

Google Chrome is preferred by some users, it uses a lot of Mozilla technology since Google supports Firefox. I believe there ought to be a pipelining method this I'll look into for now I am focusing on the Firefox browser.

Adblock I actually leave my adblock with it's default options settings, however I do have NoScript running at the same time. Do you run the most recent Firefox 3 version?

[Tartarga]

For undo the settings, just click the one you altered and set it to default. If it was an integer it will be set to 0 and a boolean to the opposite or will change it into a stinger with 0 value.
I already tested every tweak in the page 2 and it runs exactly like before, pages load faster that is, but zOMG is almost not affected (for me)


The following settings should be done in about:config (obviously).

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 an 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 this is an 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. There's no need to 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 the end.

Quick 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 I 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. I am 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

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 I 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 my configuration files however. Powerusers are also welcome to disable the status bar to eek out that extra CPU cycle or two.
I did all this in an internet cafe just to not kill my comp by testing, but don't worry, it works fine and all.
This is why I love wikias biggrin
Enjoy trying this jan mrgreen


If you guys do this and the comp is slower now, just undo everything. Set everything to default and that is all

MozillaZine thread : lul

[PowderedVinegar]

perhaps redo the thread while it's early and take page one and two.

and then, for details and advanced settings: users can go to page to, this way it's much less cluttered and users who aren't as... advanced, won;t explode from information masses XD