Browse Source

avoid thrashing the bandwidth exercise when we change IPs a lot.
(we avoid simply by not doing any new tests when we change IPs --
it looks like we retain our previous bandwidth estimates, so there's
no need to do new exercise. though in some cases new exercises may
still be useful. one day we'll do something smarter.)


svn:r8402

Roger Dingledine 19 years ago
parent
commit
a51ec44466
2 changed files with 3 additions and 2 deletions
  1. 2 1
      doc/TODO
  2. 1 1
      src/or/router.c

+ 2 - 1
doc/TODO

@@ -18,7 +18,8 @@ P       - phobos claims
       by default, if it works?"
       by default, if it works?"
 
 
 Items for 0.1.2.x, real soon now:
 Items for 0.1.2.x, real soon now:
-R - avoid thrashing the bandwidth exercise when we change IPs a lot
+R o avoid thrashing the bandwidth exercise when we change IPs a lot
+    (we avoid simply by not doing any new tests when we change IPs.)
   - When we've been idle a long time, we stop fetching server
   - When we've been idle a long time, we stop fetching server
     descriptors. When we then get a socks request, we build circuits
     descriptors. When we then get a socks request, we build circuits
     immediately using whatever descriptors we have, rather than waiting
     immediately using whatever descriptors we have, rather than waiting

+ 1 - 1
src/or/router.c

@@ -490,7 +490,7 @@ server_has_changed_ip(void)
   stats_n_seconds_working = 0;
   stats_n_seconds_working = 0;
   can_reach_or_port = 0;
   can_reach_or_port = 0;
   can_reach_dir_port = 0;
   can_reach_dir_port = 0;
-  reset_bandwidth_test();
+//  reset_bandwidth_test();
   mark_my_descriptor_dirty();
   mark_my_descriptor_dirty();
 }
 }