Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Normally the browser will make one request to a web page at a time. When you enable pipelining it will make several at once, which really speeds up page loading.
2. Alter the entries as follows:
Right click on the entries to edit.
Set "network.http.pipelining" to "true"
Set "network.http.proxy.pipelining" to "true"
Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.
3. Lastly right-click anywhere and select New-> Integer. Name it "nglayout.initialpaint.delay" and set its value to "0". This value is the amount of time the browser waits before it acts on information it recieves.
If you're using a broadband connection you'll load pages 2-3 times faster now.
Originally posted by salparadise Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.
I saw this and there's one thing that concerns me. That's the above change. I know there is software that will block IP addresses if they recieve to many requests at once. It's to help guard against DoS (Denial of Service) Attacks. I set mine at 20 and then tried 30 and saw no difference on a 1.5mb download/864kb upload connection.
EDIT: this does work, especially when going from the loading screen after you place a post back to the thread.
Originally posted by Zuggy I saw this and there's one thing that concerns me. That's the above change. I know there is software that will block IP addresses if they recieve to many requests at once. It's to help guard against DoS (Denial of Service) Attacks.
Thought of something interesting about this...
What if you were able to enter in proxy servers for each different string? That way it would not show your IP address when trying to bombard the servers like that. Now I realize this is probably counter-productive because going through the proxy would slow you down anyways... What do you guys thinK?
yes they do work, i might have to go back and adjust the max connection down from were i was told to set it to (100 btw) to something around 30 or less, but yes i did see that when i made some of the changes one of the smaller forums i post to no longer works at all in FF. this very well could be due to several of the changes as that link indicates.
I tried it on Wndoze and pages certainly seem to load far faster (when I'm not accessing dynamic pages like this one where the browser will always have to wait for the server to construct it).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.