| |||||||||||||
Increasing the TCP initial congestion windowIncreasing the TCP initial congestion windowPosted Feb 10, 2011 6:49 UTC (Thu) by mtaht (✭ supporter ✭, #11087)Parent article: Increasing the TCP initial congestion window
If google sent less data, it would also solve their problem nicely, without endangering TCP/ip.
The useful components in a google search result would fit into a single packet.
I would like it if google's search was more like DNS in structure and brevity.
(Log in to post comments)
Increasing the TCP initial congestion window Posted Feb 10, 2011 11:22 UTC (Thu) by cortana (subscriber, #24596) [Link]
I would like to see the opposite: a new DNS RR to allow DNS responses to carry advertising information!
Increasing the TCP initial congestion window Posted Feb 10, 2011 15:13 UTC (Thu) by jengelh (subscriber, #33263) [Link]
Google once was fast, now the major part of /index.html is just javascript fat.
Increasing the TCP initial congestion window Posted Feb 10, 2011 18:29 UTC (Thu) by mtaht (✭ supporter ✭, #11087) [Link]
As if breaking NXDOMAIN everywhere wasn't enough?
One DNS provider (name.com), in addition to returning ptrs to ad sites on missing domain names, is ALSO returning completely invalid pointers to IPv6 addresses for the same:
d@cruithne:~$ host no.such.subdomain.bufferbloat.net
I've been meaning to discuss this with them once I can summon the needed diplomacy and tact. So far, no luck.
Be careful what you wish for.
Increasing the TCP initial congestion window Posted Feb 10, 2011 22:14 UTC (Thu) by cortana (subscriber, #24596) [Link]
Of course, my suggestion was made in jest. However... given that ISPs are already breaking DNS by replacing NXDOMAIN responses with forged records... would we not all be better off if they were allowed to do so by the protocol? As long as there was a flag in each RR indicating that it is an advertising result, users of web browsers could opt in/out of receiving them, and other programs could ignore them altogether. At least we'd be in a better situation to that which we are in now. Of course, DNSSEC presumably fixes all of this, but not in favour of those who are incentivized to present the forged advertising responses.
Increasing the TCP initial congestion window Posted Feb 10, 2011 16:19 UTC (Thu) by tstover (subscriber, #56283) [Link]
spot on.
I'm still waiting for gopher 2.0 with, say, links in utf-8 text.
Increasing the TCP initial congestion window Posted Feb 10, 2011 17:15 UTC (Thu) by mtaht (✭ supporter ✭, #11087) [Link]
At the risk of over-promoting myself, I got fed up with google's default search a few months back and (re)wrote a command line client, called gnugol, to make my life simpler and faster - and far less annoying again.
It works the command line and in emacs.
The latency improvement is remarkable. The S/N ratio is nice too.
Originally, it was a client/server protocol that ran over udp, I've been thinking of resurrecting the server piece, possibly using sctp, as I think latency can be further improved with a persistent connection for search.
Google's search IS so fast that in many cases the RTT for initial TCP setup dominates the entire session - I can get a 50ms response for a query located 2ms from google, and 200ms (at best) for one from Colorado.
I would certainly like more people to give the idea and tool a shot.
Gnugol also supports bing and a few other search engines - I thought what I wrote here about stackoverflow's interface, vs gnugol's to be pretty damning.
http://nex-6.taht.net/posts/Screen_Space/
|
|||||||||||||