Does it work really?

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
minegroasprilla

Does it work really?

Post by minegroasprilla » 2011-09-02, 23:08

Some webs explain how to speed Firefox (Pale Moon).
The common method is:
- network.http.pipelining to "true"
- network.http.proxy.pipelining to "true"
- network.http.pipelining.maxrequests to "30"

My question about this method on Pale Moon is, Does it work really?

diNovoM

Re: Does it work really?

Post by diNovoM » 2011-09-02, 23:23

Sure this works, just that network.http.pipelining.maxrequests is set to "16", you still can max it up if you have a real fast connection. Default FF is 8 i believe? However, you can open about.config, enter network.http. and check which settings are default (at least if you didn't change them/import a profile or temporary reset them).

User avatar
Moonchild
Project founder
Project founder
Posts: 38821
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Does it work really?

Post by Moonchild » 2011-09-02, 23:56

diNovoM wrote:Sure this works, just that network.http.pipelining.maxrequests is set to "16", you still can max it up if you have a real fast connection.
There's a lot of confusion about that parameter. People don't seem to understand how it works :)
Making the number (much) higher actually makes things worse.
the maxrequests parameter tells Pale Moon how many requests send out at once before requiring a server response. If you make this value too high, the browser will slow its page loading since everything is "queued up" in the pipelines.

Firefox by default doesn't use pipelining. This means that for each element on the page, a one-on-one request and response communication occurs.
Pale Moon uses pipelining with a maxrequest of 16. This means that up to 16 elements requested at once to be transported. Often, this means that small elements can be packed together in single TCP/IP packets on the network, dramatically increasing the transfer speed and efficiency.
If you tweak it too high, then responses from the server can get backed up or even canceled out. You don't want that.

More background information on pipelining: http://www-archive.mozilla.org/projects/netlib/http/pipelining-faq.html

PS: pipelining through a proxy server is disabled by default in Pale Moon, because a good number of proxy servers don't handle this very well, and can actually completely stall out page loading.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

diNovoM

Re: Does it work really?

Post by diNovoM » 2011-09-03, 00:24

It seems i mixed up s.t. here, 16 will be more than enough, some recommend even 6 only, ff default is 2. What i didn't get till now is that thing about proxy.pripes - seems i looked in the wrong line or something, always thought it would be true. Still network.http.max-persistent-connections-per-proxy is set to 8 instead of 4 in ff.

Also there are other options like for memory/disc/dns cache, *max-connections*, *persistent-connections*,

User avatar
Moonchild
Project founder
Project founder
Posts: 38821
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Does it work really?

Post by Moonchild » 2011-09-03, 00:34

Trust me when I say that I've set sane defaults for all of those :)
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite