Redirect handling in resource prefetch predictor

chrome/browser/predictors/resource_prefetch_common.h

Index: chrome/browser/predictors/resource_prefetch_common.h
diff --git a/chrome/browser/predictors/resource_prefetch_common.h b/chrome/browser/predictors/resource_prefetch_common.h
index 33812ff5183a9975a1ca432698b828bb81cab67c..8d18afdf63c55c5b53efb450c000c08bfd2fa889 100644
--- a/chrome/browser/predictors/resource_prefetch_common.h
+++ b/chrome/browser/predictors/resource_prefetch_common.h
@@ -104,6 +104,8 @@ struct ResourcePrefetchPredictorConfig {
 
   // The maximum number of resources to store per entry.
   size_t max_resources_per_entry;
+  // The maximum number of redirects to store per entry.

[Benoit L, 2016/09/19 13:53:47]

I'm not 100% sure that we really need a setting for this. Generally speaking,
less knobs is better.

The settings above were used to tune parameters for experiments. Unless we have
a good reason to do otherwise, maybe we can start with keeping a small fixed
number of entries.

My suspicion is that the redirect chains are going to be either "monomorphic" or
"megamorphic". The second case we don't care about.

+  size_t max_redirects_per_entry;
   // The number of consecutive misses after we stop tracking a resource URL.
   size_t max_consecutive_misses;