Deciding best connection to schedule requests on based on cwnd and idle time

chrome/common/chrome_switches.h

Index: chrome/common/chrome_switches.h
===================================================================
--- chrome/common/chrome_switches.h	(revision 88319)
+++ chrome/common/chrome_switches.h	(working copy)
@@ -257,6 +257,7 @@
 extern const char kSyncNotificationHost[];
 extern const char kSyncServiceURL[];
 extern const char kSyncTrySsltcpFirstForXmpp[];
+extern const char kTcpSocketEstimatedCwndDecayCoef[];

[Mike Belshe, 2011/06/09 16:08:52]

yeah - seems too deep to expose this

[Gagan, 2011/06/09 19:49:26]

i want to be able to specify the value directly on command line for
experimentation with different values.
I want to try this out on say webpagetest.

[Mike Belshe, 2011/06/10 18:11:42]

That seems wrong to me, you're violating common encapsulation - you've put the
policy into the browser_main, and code in the net layer.

Do you really need to test arbitrary values on webpagetest?  Those will be
anecdotal results anyway.  Picking some specific damping coefficients and then
using the A/B test that you've got is superior.


On 2011/06/09 19:49:26, gagan.goku wrote:

[Gagan, 2011/06/12 20:11:44]

Done.

 extern const char kTestNaClSandbox[];
 extern const char kTestName[];
 extern const char kTestType[];