Quote
caktus
Quote
An other slimmed down Lizard..BUT WITH THE FAMOUS 8 PIPELINING REQUEST LIMIT REMOVED.
What would this accomplish? Would PIPELINING REQUEST be infinitive (what ever the web site or host permit)?
Would increasing or removing network.http.pipelining.maxrequests from 1.5.1 be safe or helpful?
That would make it faster...
And no the max PIPELINING REQUEST would not be infinite..Nope...Instead the user will have the chance to ADJUST THE LIMIT ACORDING WITH THE SERVER`S CAPACYTY..
That`s how i see it..
Now...You have to realize that nowadays there 90% users out there using the 1980`s network protocol...eh,,,? Users who never heard about super jumboframes and stuff..
Users who are still surfing the net with the original 1,518-byte MTU....and only 2 if that PIPELINING REQUESTS ..
Now by increasing the limit to a resonable number you can increase the speed is as simple as that...
If you go crazy with the PIPELINING REQUESTS you can get your connection dropped or refuzed..But if you fine tune it...You`re a winner...
That`s the whole ideia behind this experiment...
People does not really realize that servers all around the world are dealing with MORE THAN 8 PIPELINING REQUESTS /sec on a daily basis..otherwise they won`t be able to function..So the capacity exists...Is there .If it is not used is because the DEVS ARE FOLLOWING BLINDLY THE SAME STEPS IN COMPILING THE BROWSER...
Which is ok with me because if i go out there in the www (WILD WILD WEB
) with a PIPELINING REQUESTS limit removed i am a winner...I WILL BE ABLE TO CONNECT TO THE SERVER GET WHAT I REQUESTED FASTER THAN ANYONE ELSE ,
AND AFTER THAT LEAVE THE CONNECTIONS OPPENED FOR THE OTHER GUYS...SAVING TIME MONEY AND RESURCES...FOR THE SERVER....AS LONG S I DO NOT GO CRAZY WITH THE PIPELINING REQUESTS SETTINGS
Think about it...
LET'S take a look at youtube :it is extremly bussy and loaded with huge melodies and video..Every time a normal user connects there using the normal network protocol and a normal internet connection and request a melody(audio-video stream
opens up few connections AND KEEPS THE OPPENED UNTILL THE GUYS HAS FINISHED DOWNLOADING THE MELODY,AND THE DEPENDING ON USER`S TTL, KEEPS IT A LITTLE BIT MORE..JUST IN CASE..That's fine if you live in 80's when the internet was not like nowadays...
Ok...now picture the above scenario...only add 100 more millions of users per second which access the server from all of the corners of the planet..
A NORMAL USER WILL KEEP OPENED THE FEW CONNECTIONS HE HAS UNTIL HE HAS FINISHED THE MELODY download because HE ONLY IS PERMITED FEW,and no pipelining if he uses IE...he is going to KEEP THE CONNECTIONS OPENED AND LOCKED FOR HIMSELF A LOT MORE A LOT MORE THAN a user that has enabled jumbo frames and comes with a customized browser that enables him to request like 300 pipelining request per second an an other few hundred in the total connection per server area..
Now the customized browser guy is goin' to finish the melody download in 5 SECONDS and go away LIVING THE CONNECTIONS AVAILABE FOR THE OTHER GUYS AND THEREFORE MINIMALIZING THE IMPACT ON THE SERVER RESURCES ...whereas the regular browser guys are going to stick there on the server like a 500kg handicapated 2 years old kid forcing his mother to fill up his huge stomack (Otherwise they won't let her go and won't shut the f...ck up!!!
) the food in this case is the melody which a normal user needs to download and the kid is the browser with a normal internet connection
So you see.. in a modern world scenario the old network connection protocol is kind of obsolete..