seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2020/02/25, 15:49:05


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Iceweasel speedup hint  (Read 1489 times)

0 Members and 1 Guest are viewing this topic.

Offline GoinEasy9

  • User
  • Posts: 461
Iceweasel speedup hint
« on: 2014/05/15, 07:57:27 »
I was reading how older versions of Firefox could be sped up by using "network.http.pipelining”.  There were a host of additions that were to be added to about config, but, that was before version 29. 

So, I looked up "network.http.pipelining” in the about:config of 29 and saw that it was disabled (set to false).  So I set it to true and saw a noticeable speed boost loading pages.  In the older versions, setting maxrequests over 8 was redundant, but, in version 29, maxrequests was preset for 32. 

I wonder why the default was set to false?  I'm also wondering if I should set "network.http.pipelining-ssl also to true.  I'm still looking, but, I thought I'd post to see if anyone else has used pipelining to speed up Iceweasel.  Anyone?
Linux Counter number 348347

Offline der_bud

  • User
  • Posts: 901
  • member
Re: Iceweasel speedup hint
« Reply #1 on: 2014/05/15, 09:10:07 »
Once upon a time :) there have been a lot of posts regarding firefox speed optimization, most of them playing around with all the "network.foo.bar" settings.
They did work, as old defaults considered slower modem connections, while powerusers already had broadband. Some of those settings (like maxrequest) had a lower default because the could be considered unfair if too many people do to many requests at servers.
Whether all these optimization settings now are just voodoo or play any role on modern systems with providers on powerful backbones, I do not know. But I seldom set up a new firefox-profile, so during the years I have still all the old optimization settings in my about:config.

You can read up those settings, the defaults and what they do at mozillazine, for example
http://kb.mozillazine.org/Network.http.pipelining
http://kb.mozillazine.org/Network.http.pipelining.maxrequests
and so on.

Last time I got my settings from a german firefox forum, from my bookmarks it could have been
this post: http://www.camp-firefox.de/forum/viewtopic.php?f=7&t=30873&start=2850#p788126
or this: http://www.camp-firefox.de/forum/viewtopic.php?f=7&t=30873&start=2790#p724910

-

EDIT: Here one more discussion, this time english language, in mozillazine forum:
 http://forums.mozillazine.org/viewtopic.php?f=23&t=2450483 . Let me quote the last post:
Quote
"Yeah.. those of us that used all the Internet Geek Speed Twreaks in the Firefox 3.x days need to reevaluate. For example the default setting for the newer Firefox versions for network.http.max-connections is now 256 so the 48, 96, 128 we all used is giviing us less than the default settings since Firefox 10. And other like content.interrupt.parsing dont even exist. "

« Last Edit: 2014/05/15, 09:42:30 by der_bud »
Du lachst? Wieso lachst du? Das ist doch oft so, Leute lachen erst und dann sind sie tot.

Offline seasons

  • User
  • Posts: 241
Re: Iceweasel speedup hint
« Reply #2 on: 2014/06/05, 07:09:57 »
I wonder why the default was set to false?
"not all servers support it. Some servers may even behave incorrectly if they receive pipelined requests"
-- http://kb.mozillazine.org/Network.http.pipelining

Quote
I'm also wondering if I should set "network.http.pipelining-ssl also to true.
No need to do that if network.http.pipelining is set to true

"If this preference is false and network.http.pipelining is true, pipelining will still be used for secure websites."
-- http://kb.mozillazine.org/Network.http.pipelining.ssl