Default socket reuse policy -- why is "last accessed" the default policy ?
15 views
Skip to first unread message
msc...@viasat.com
May 15, 2012, 3:02:01 PM5/15/12
to Chromium-discuss
Why is the default socket-reuse-policy set to USE_LAST_ACCESSED_SOCKET
by default ?
Wouldn't it be better to use USE_WARMEST_SOCKET or even
USE_WARM_SOCKET or as the default so that we are more likely to have
passed the slow-start phase of TCP ?
There appears to be some sort of field trial going on if the policy is
not set on the command line.
ref...
void ChromeBrowserMainParts::WarmConnectionFieldTrial()
by default ?
Wouldn't it be better to use USE_WARMEST_SOCKET or even
USE_WARM_SOCKET or as the default so that we are more likely to have
passed the slow-start phase of TCP ?
There appears to be some sort of field trial going on if the policy is
not set on the command line.
ref...
void ChromeBrowserMainParts::WarmConnectionFieldTrial()
Chris Bentzel
May 15, 2012, 4:15:34 PM5/15/12
to msc...@viasat.com, Chromium-discuss, Jim Roskind, Matt Menke, William Chan
Added a few folks who might know.
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss
Reply all
Reply to author
Forward
0 new messages