|
阅读：4119回复：9
content.notify.backoffcount是什么用的？兼转载一篇优化提速文章
content.notify.backoffcount
在知识库里没找到 但老外的优化设置里看到的 另外，转载一篇论坛看到的提速文章， 地址：http://www.extensionsmirror.nl/index.php?showtopic=2875 内容如下： This is a more in depth guide to speeding up Mozilla Firefox than some other guides. This guide was made so that any computer could become faster, not just a fast computer with a fast connection. First, install the ChromEdit extension. It make it easier to edit user files. Now, run Firefox, go to Tools > Edit User Files, click user.js tab. Insert the following texts based on your PC speed and internet connection. Here's a little key: Fast Computer is greater than 1.5Ghz CPU and atleast 512MB RAM Fast Connection is DSL or cable or better. 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. Common to all configurations CODE /* Speed Tweak - Common to all Configurations */ 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 CODE /* Speed Tweak - 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. This configuration is more suited to people without ultra fast connections. We are not talking about dial up connections but slower DSL / Cable connections. Fast Computer, Slower Connection CODE /* Speed Tweak - Fast Computer, Slower 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("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 CODE /* Speed Tweak - 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 CODE /* Speed Tweak - 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. We have entered the doldrums of the dial-up user Slow Computer, Slow Connection CODE /* Speed Tweak - 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); Another Tweak CODE /* Speed Tweak - Another Tweak */ user_pref("network.dns.disableIPv6", true); This tweak deactivates IPv6 in Firefox, because most if not all of the web is still using IPv4. IPv4 and v6 are internet protocols... how the data is transferred... v4 is the standard now and v6 is slowly being implemented around the world... it wont come into full swing until 2008-2010 sadly... it's a huge infrastructure change, but the benefits will be great. |
|
|
1楼#
发布于：2005-10-25 20:35
太多了 能不能简明扼要一些 说明一下 什么chromeedit哪里可以下载?
|
|
|
|
2楼#
发布于：2005-10-25 20:35
|
|
|
|
3楼#
发布于：2005-10-25 20:35
|
|
|
|
4楼#
发布于：2005-10-25 20:35
copy~哈
|
|
|
|
5楼#
发布于：2005-10-25 20:35
好像前段时间宇宙火星早就发过了，很有用的
|
|
|
6楼#
发布于：2005-10-25 20:35
宇宙火星早就发过了
|
|
|
7楼#
发布于：2005-10-25 20:35
哦，发过了
那有人知道content.notify.backoffcount 是什么意思吗？ 具体有什么功能？？ |
|
|
8楼#
发布于：2005-10-25 20:35
|
|
|
9楼#
发布于：2005-10-25 20:35
找到了，不过太专业，不懂
Tuning Pageload From Devmo Tuning pageload can be beneficial if you know what you're doing. Firefox (and all Mozilla Products/Projects which do page-loading) ship with what is considered the "best" settings for the most cases. This document explains which preferences to tweak to affect your pageload time. You use the url about:config or the file prefs.js in your profile to change these. To best understand what the following preferences affect, there are a few things you should know. * The data flows in Gecko as follows: network -> necko -> parser -> content sink -> content model -> rendering model -> layout -> painting. nglayout.initialpaint.delay This is a preference that specifies a delay, in milliseconds, after the data from the server has started coming in. During this delay, the page that's coming in is not painted, unless it ends up fully loaded before the delay expires. The idea here is twofold. * This reduces ugly visual jitter as the new page comes in by not starting painting till after we have a bunch of the data. * This makes overall page load time shorter by not doing extra repaints very early on. content.interrupt.parsing This preference, when true, means that the content sink can tell the parser to stop for now and return to the event loop, which allows layout and painting to happen. If the parser gets a large chunk of data, it will try to parse it all, building the corresponding content model. Since layout and painting happen asynchronously, while the parser is working there is no layout or painting. So this preference is used to increase responsiveness, especially on cached loads (where data comes into the parser in large chunks) content.max.tokenizing.time Controls how often the sink interrupts the parser. The parser is interrupted at least every content.max.tokenizing.time microseconds, if it can be interrupted at all; bug 76722 may have more details on this part. content.switch.threshold Determines how often we switch content sink modes. There are two modes. In mode A we interrupt the parser every content.max.tokenizing.time microseconds. In mode B we interrupt the parser every 3000 microseconds. Every content.switch.threshold microseconds, we decide whether we should be in mode A or mode B. The decision is based on whether there were any user events on the relevant widget in the last content.switch.threshold microseconds. As in, if the user is moving the mouse or typing in that window, we'll be more responsive; if there is no user activity, we will aim for less parser interruption and less responsiveness but lower overall load time. content.notify.* Controls the information flow from content sink to rendering model. In particular, the way things work right now is that the parser and content sink construct the DOM; then every so often, the content sink lets the rendering model constructor (nsCSSFrameConstructor) know that there are new DOM nodes. The reason for this is that nsCSSFrameConstructor is most efficient when doing a bunch of stuff at once instead of constructing rendering objects for one DOM node at a time. specifically - content.notify.ontimer controls whether the frame constructor is notified off a timer at all content.notify.backoffcount controls how many times that happens for a given page (the default is arbitrarily many times). Once the backoff count is reached, no more rendering model construction till after the whole page is parsed. content.maxtextrun Controls the maximum length of data in a TextNode. So if you have more than content.maxtextrun characters of text in a row, we'll create multiple textnodes for it. this is an optimization designed to prevent long text from ending up being O(N^2). It's also really a bug per the DOM spec and we should stop doing it... |
|
