diff options
| author | Nick Mathewson <nickm@torproject.org> | 2011-01-10 14:11:22 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2011-01-10 14:47:39 -0500 |
| commit | 105b94b75b51376128037cab05b930c4e4c15497 (patch) | |
| tree | 6e439b3b5d8a716e6c1dff3e9f1eee4ca15fba37 /changes/1863_bwhist | |
| parent | 28844c8403f16f184c185798c78dcd6a959450a3 (diff) | |
| download | tor-105b94b75b51376128037cab05b930c4e4c15497.tar.gz tor-105b94b75b51376128037cab05b930c4e4c15497.zip | |
Add Maxima lists to bandwidth state.
Right now, Tor routers don't save the maxima values from the
bw_history_t between sessions. That's no good, since we use those
values to determine bandwidth. This code adds a new BWHist.*Maximum
set of values to the state file. If they're not present, we estimate
them by taking the observed total bandwidth and dividing it by the
period length, which provides a lower bound.
This should fix bug 1863. I'm calling it a feature.
Diffstat (limited to 'changes/1863_bwhist')
| -rw-r--r-- | changes/1863_bwhist | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/changes/1863_bwhist b/changes/1863_bwhist index b9e8ef4c52..b94250906b 100644 --- a/changes/1863_bwhist +++ b/changes/1863_bwhist @@ -1,3 +1,10 @@ + o Minor features + - Servers now save observed maximum bandwidth throughput rates + to their state file (along with total usage, which was already + saved) so that they can determine their correct estimated + bandwidth on restart. Resolves bug 1863, where Tor servers + would reset their estimated bandwidth to 0 after restarting. + o Minor bugfixes - Fix a bug in banwidth history state parsing that could have been triggered if a future version of Tor ever changed the timing @@ -7,4 +14,3 @@ error parsing any bw history value from the state file. Bugfix on Tor 0.2.2.15-alpha. - |