[Webkit-unassigned] [Bug 137282] [SOUP] Consider reducing max simultaneous connections

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=137282





--- Comment #1 from Sergio Villar Senin <svillar at igalia.com>  2014-10-01 00:15:44 PST ---
(In reply to comment #0)
> I noticed this code in Source/WebCore/platform/network/soup/SoupNetworkSession.cpp:
> 
>     // Values taken from http://www.browserscope.org/ following
>     // the rule "Do What Every Other Modern Browser Is Doing". They seem
>     // to significantly improve page loading time compared to soup's
>     // default values.
>     static const int maxConnections = 35;
>     static const int maxConnectionsPerHost = 6;
> 
> I checked Browserscope [1], and Firefox, Internet Explorer, and Safari all allow 17 connections nowadays. Chrome only allows 10. I have no clue if reducing max connections will improve performance, but I like the sound of "Do What Every Other Modern Browser Is Doing"....
> 
> [1] http://www.browserscope.org/?category=network&v=top

In general a higher amount of max_connections allows more parallelism, and thus faster downloads. Said that, the only reason to limit that number (apart from not overflowing your router's NAT) is to be "nice" with the servers and the other clients.

There should be a reason why they lowered that number, perhaps server admins are actually reducing that number.

In any case I'm pretty sure that if FF, IE and Safari have a lower number right now it's because they have deeply studied all the consequences and concluded that having half the connections is better.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.