#14881 closed defect (fixed)
incorrect defaults when producing bandwidth-weights line in directory footer
Reported by: | robgjansen | Owned by: | pastly |
---|---|---|---|
Priority: | Medium | Milestone: | Tor: 0.3.0.x-final |
Component: | Core Tor/Tor | Version: | Tor: 0.2.7 |
Severity: | Normal | Keywords: | 027-triaged-1-in, 028-triaged, pre028-patch, tor-sponsorU-orphan, TorCoreTeam-postponed-201604, nickm-deferred-20161005, review-group-10 |
Cc: | arma | Actual Points: | |
Parent ID: | Points: | 3 | |
Reviewer: | mikeperry | Sponsor: | SponsorU-can |
Description
When running Tor in small testing networks, much of the time the bandwidth-weights line does not appear in the directory-footer in the consensus files. The log file shows messages like this:
Consensus with empty bandwidth: G=852123 M=0 E=0 D=569253 T=1421376
The code that counts up these bandwidth values is in networkstatus_compute_consensus
in dirvote.c
, specifically around line 1590 in Tor master as of now.
The code that prints this error is in networkstatus_compute_bw_weights_v10
in dirvote.c
.
I believe that it is an error not to produce bandwidth-weights in the event that we have no knowledge of bandwidth for a given position. For example, if D is zero because there are no nodes that serve as exits+guards, shouldn't we just adjust the weights accordingly? We may still have functional guards and functional exits just because we have no node that serves as both.
Since this is for weighting purposes, why are T, D, E, G, and M all initialized to 0 instead of 1? I think the default weight should be 1, meaning all positions are selected equally, and any bandwidth above 1 should be used to increase the weight. Does this sound right?
If that is not desired, then I request that we at least initialize these values to one for testing networks. One patch is attached for each of these options.
Child Tickets
Attachments (11)
Change History (78)
Changed 5 years ago by
Attachment: | 0001-initialize-bw-to-1-in-testing-networks-when-producin.patch added |
---|
Changed 5 years ago by
Attachment: | 0001-initialize-bw-to-1-when-producing-bw-weights.patch added |
---|
patch to change in all cases
comment:1 Changed 5 years ago by
Milestone: | → Tor: 0.2.7.x-final |
---|---|
Status: | new → needs_review |
comment:2 Changed 4 years ago by
Status: | needs_review → needs_revision |
---|
We can't change the behavior of this function without updating the consensus method. Also, needs a changes file.
comment:3 Changed 4 years ago by
Keywords: | 027-triaged-1-in added |
---|
Marking more tickets as triaged-in for 0.2.7
comment:4 Changed 4 years ago by
Keywords: | SponsorU added |
---|---|
Points: | → medium |
Version: | Tor: unspecified → Tor: 0.2.7 |
comment:5 Changed 4 years ago by
Milestone: | Tor: 0.2.7.x-final → Tor: 0.2.8.x-final |
---|
comment:6 Changed 4 years ago by
Keywords: | 028-triaged added |
---|
comment:7 Changed 4 years ago by
Keywords: | SponsorU removed |
---|---|
Sponsor: | → SponsorU |
Bulk-replace SponsorU keyword with SponsorU field.
comment:8 Changed 4 years ago by
Keywords: | pre028-patch added |
---|
comment:9 Changed 4 years ago by
Owner: | set to robgjansen |
---|---|
Severity: | → Normal |
Status: | needs_revision → assigned |
Setting robgjansen as the owner of this needs_revision ticket.
comment:10 Changed 4 years ago by
Status: | assigned → needs_revision |
---|
comment:11 follow-up: 12 Changed 4 years ago by
What is requested of me here? Do I simply need to increment the a consensus version counter somewhere, and add a blurb to the changelog, and attach a new patch? Am I mistaken in thinking that these are trivial additions? Or is there something complex that I am overlooking?
comment:12 Changed 4 years ago by
Replying to robgjansen:
What is requested of me here? Do I simply need to increment the a consensus version counter somewhere, and add a blurb to the changelog, and attach a new patch? Am I mistaken in thinking that these are trivial additions? Or is there something complex that I am overlooking?
Adding a consensus method means:
- adding a
#define MIN_METHOD_FOR_INIT_BW_WEIGHTS_ONE 22
- updating
#define MAX_SUPPORTED_CONSENSUS_METHOD 22
- keep the old behaviour when
consensus_method < MIN_METHOD_FOR_INIT_BW_WEIGHTS_ONE
, that is, the consensus method supported by the majority of the authorities does not include the changes - use the new behaviour when
consensus_method >= MIN_METHOD_FOR_INIT_BW_WEIGHTS_ONE
And then making sure that when we merge, each consensus method actually gets a different number.
comment:13 Changed 4 years ago by
Milestone: | Tor: 0.2.8.x-final → Tor: 0.2.9.x-final |
---|
These seem like features, or like other stuff unlikely to be possible this month. Bumping them to 0.2.9
comment:14 Changed 3 years ago by
Sponsor: | SponsorU → SponsorU-can |
---|
comment:15 Changed 3 years ago by
Done: https://github.com/robgjansen/torclone/tree/tor-14881
Do I also need to add a blurb to the changelog? Or is that done by the merger?
comment:16 Changed 3 years ago by
You add a file to the changes directory, as described in doc/HACKING/CodingStandards.md, in the section labeled "How we log changes".
comment:17 Changed 3 years ago by
OK, added this all in a single commit. The specific commit is here:
https://github.com/robgjansen/torclone/commit/b110b307bb1e66abe5c9ad6a19eea7e5323fe740
comment:18 Changed 3 years ago by
Status: | needs_revision → needs_review |
---|
comment:19 Changed 3 years ago by
Keywords: | TorCoreTeam201604 added |
---|
Every postponed needs_review ticket should get a review in April
comment:20 Changed 3 years ago by
Reviewer: | → mikeperry |
---|
Mike, I think you might be the logical best reviewer for this. Please let me know if that's not right, or if you don't have time.
comment:21 Changed 3 years ago by
Keywords: | tor-sponsorU-orphan added |
---|
comment:22 Changed 3 years ago by
Status: | needs_review → needs_revision |
---|
First thoughts: Does this run without printing out additional errors? networkstatus_check_weights() verifies that the linear algebra has a consistent solution and will cause a warn to be emitted if not, and the weights will still be omitted. At minimum, for full correctness I think we need to initialize T to 4 here, if we initialize all other weights to 1. Technically we're also introducing a slight inaccuracy by this method of initialization, as well (since we're giving every node class a tiny bit of weight that isn't actually there).
It may also be the case that we were within a rounding error of correctness, and so this ran OK.
I think this might mean that it would be simplest for this change to apply to testing networks only. Perhaps we just have a testing network check at the top of networkstatus_compute_bw_weights_v10() that sets weights to 1 only if it is a testing network and they are zero.
Give me a second and I will attach an alternate (untested) patch just for testing networks.
Changed 3 years ago by
Attachment: | 0001-Untested-alternate-bug-14881-solution.patch added |
---|
Untested alternate patch for testing networks.
comment:23 follow-up: 25 Changed 3 years ago by
Note: I didn't bump the consensus method for that, nor add a changes file... Not sure if we need a consensus method just for a testing network change. Also not sure if Rob really needs this to apply to testing networks that don't think they are testing networks.. In either case, this may be more complicated.
comment:24 Changed 3 years ago by
Shadow Tor networks still think they are testing networks :) I personally have no need for it outside of testing networks.
comment:25 Changed 3 years ago by
Replying to mikeperry:
Note: I didn't bump the consensus method for that, nor add a changes file... Not sure if we need a consensus method just for a testing network change. Also not sure if Rob really needs this to apply to testing networks that don't think they are testing networks.. In either case, this may be more complicated.
We need a new consensus method, or this change will break the "mixed" chutney target.
(Which exists to find exactly this kind of breakage.)
It's run during make test-network-all, which may soon be in our jenkins builds. So let's so it the right way :-)
comment:26 Changed 3 years ago by
Keywords: | TorCoreTeam201605 TorCoreTeam-postponed-201604 added; TorCoreTeam201604 removed |
---|
April is over; calling these april tickets postponed into may.
comment:27 follow-up: 31 Changed 3 years ago by
Rob, do you think you can merge my mock-up patch with the consensus method check and create a new proper patch? I am juggling a few too many things this week.
comment:28 Changed 3 years ago by
My May has already become far too loaded. It's better that I be honest and say no rather than agreeing to it and then dropping it on the floor. Sorry!
comment:29 Changed 3 years ago by
Points: | medium → 3 |
---|
comment:30 Changed 3 years ago by
Keywords: | TorCoreTeam201605 removed |
---|
Remove "TorCoreTeam201605" keyword. The time machine is broken.
comment:31 Changed 3 years ago by
Replying to mikeperry:
Rob, do you think you can merge my mock-up patch with the consensus method check and create a new proper patch? I am juggling a few too many things this week.
I've run into this issue working on KIST stuff like Rob probably did a while ago.
I'm uploading a merge of your mock-up patch and Rob's "testing network only" patch. This doesn't add a new consensus version, it should just sets the weights to 1 if testing.
I'll be testing this patch shortly
Changed 3 years ago by
Attachment: | 0001-merge-calc-and-initialization-testing-only.patch added |
---|
comment:32 Changed 3 years ago by
My previous comment still applies, if we merge this latest patch, it will break the chutney "mixed" version target. Even if it only breaks test networks, it's still breakage. To merge it into Tor, we need a new consensus method.
We might also want to resolve mikeperry's concerns before we merge:
"for full correctness I think we need to initialize T to 4 here, if we initialize all other weights to 1".
comment:33 Changed 3 years ago by
Owner: | changed from robgjansen to pastly |
---|---|
Status: | needs_revision → assigned |
I'll take a look at this today/this weekend.
wrt to initializing to 1 vs. falling back to 1 (Rob's initial patch vs. mikeperry's initial patch): I'm guessing both will not be necessary. Before I actually really look at the code, I'm thinking the new consensus method should only fall back to 1.
comment:34 Changed 3 years ago by
I pushed a branch to my public tor repository on github. It's based on a slightly outdated release-0.2.8.
https://github.com/pastly/public-tor/tree/ticket14881
I will also upload yet another patch, if that's easier. (Please let me know either way for future reference).
I decided to initialize to 1 instead of falling back on 1 based on teor's suggested MIN_METHOD_FOR_INIT_BW_WEIGHTS_ONE
and despite mikeperry's concern about minor inaccuracy.
Changed 3 years ago by
Attachment: | 0001-new-consensus-method.patch added |
---|
comment:35 Changed 3 years ago by
Status: | assigned → needs_review |
---|
comment:36 Changed 3 years ago by
Keywords: | review-group-8 added |
---|
comment:37 Changed 3 years ago by
Status: | needs_review → needs_revision |
---|
Thanks for getting this into usable form! We're almost there.
Branches are easier, but we'll take either.
Major issues:
- Consensus method number 23 is already MIN_METHOD_FOR_SHARED_RANDOM. Please rebase on Tor master, and use consensus method number 24 for MIN_METHOD_FOR_INIT_BW_WEIGHTS_ONE.
Minor issues:
- The spacing in the changes file does not match the spacing in other changes files. This would require a manual tweak when producing the changelog, let's fix it now.
Comments:
- This changes behaviour in all tor networks, which is correct, but riskier. It does introduce a small inaccuracy into the public network consensus weights, but only 1/10000 (BW_WEIGHT_SCALE/bwweightscale).
- Test networks will execute networkstatus_compute_bw_weights_v10 "Case 2b", rather than the "Consensus with empty bandwidth" error case. Have you verified which sub-case of 2b they execute? Does this execute without any errors? I can do this check with chutney if you'd like.
- Similarly, have you verified that the case that's executed in the current tor network works? Does this execute without any errors? It might be worth writing unit tests for each case with the new defaults, if these unit tests don't exist already.
- Have you verified that the code is compatible with a mixed-version network? Chutney has a "mixed" target for this, but you must sym/hard link your current version of tor to tor-stable somewhere in your path.
comment:38 Changed 3 years ago by
Also, this change requires a dir-spec patch, split off #20060 for that.
comment:39 follow-up: 40 Changed 3 years ago by
New rebased branch includes changelog spacing fix and 23->24.
https://github.com/pastly/public-tor/tree/ticket14881-v2
- 1/10000 does not sound like a lot to me. If this is a big enough concern, we'll have to figure something else out.
- I have not done any testing regarding which code paths differently configured relays take. I use Shadow for the work I'm currently doing, and Shadow does not support simulating a network with different versions of Tor. I have never used Chutney. FWIW, a homogeneous network executes the new method fine.
comment:40 follow-up: 57 Changed 3 years ago by
Replying to pastly:
New rebased branch includes changelog spacing fix and 23->24.
https://github.com/pastly/public-tor/tree/ticket14881-v2
- 1/10000 does not sound like a lot to me. If this is a big enough concern, we'll have to figure something else out.
I'm not worried about the inaccuracy, but I'd like to know what the impact is - where does the extra weight change which nodes we choose, and how often? Which nodes get chosen more often because of it?
- I have not done any testing regarding which code paths differently configured relays take. I use Shadow for the work I'm currently doing, and Shadow does not support simulating a network with different versions of Tor. I have never used Chutney. FWIW, a homogeneous network executes the new method fine.
Thanks for checking this. The public Tor network almost always runs with mixed authority versions, so we must test this case using chutney or a similar tool.
Can you write unit tests for each case with the new defaults?
(Are there unit tests for each case with the old defaults? We should test both.)
Have you tested using actual bandwidth weights (like the ones in the current Tor network)?
A unit test would be good for this too.
We're almost there, thanks for helping out with this.
comment:41 Changed 3 years ago by
Keywords: | review-group-9 added; review-group-8 removed |
---|
comment:42 Changed 3 years ago by
I've figured out the bare basics of chutney. I ran two simulations: one 'basic-min' with the new code and one 'basic-min-mixed' with new code and 0.2.7.6.
I will attach the data directories from each.
The mixed network uses consensus method 20 and the homogeneous network uses 24, the new one.
I'll need a little hand holding or pointing in the right direction if you still want me to write unit tests. I haven't written any tests for anything ever (gasp!)
Changed 3 years ago by
Attachment: | nodes.basic-min.ticket14881.tar.xz added |
---|
Changed 3 years ago by
Attachment: | nodes.basic-min-mixed.ticket14881.tar.xz added |
---|
comment:43 Changed 3 years ago by
Thanks for running the chutney tests.
To write a unit test for networkstatus_compute_bw_weights_v10
, you can add a function to src/test/test_dir.c
, using the existing tests as an example.
Write a tests to exercise each of the cases in that function, and check that the results are as expected. (It would also be nice to write a test for the current values in a recent consensus.)
The tor unit tests are run using:
make test
Or, for individual unit tests:
make src/test/test && src/test/test <name-of-test>
comment:44 follow-up: 45 Changed 3 years ago by
Status: | needs_revision → needs_review |
---|
I've updated my public branch with tests. In comments I mention limitations due to #20272 and #20285.
teor: you mention it would be nice to have a test with values from a recent consensus. I agree. Where can I find recent real input values M
, G
, etc. that went into producing Wxx
values? Will an authority need to be nice and share a line from his log with us?
comment:45 Changed 3 years ago by
Cc: | arma added |
---|---|
Status: | needs_review → needs_revision |
Replying to pastly:
I've updated my public branch with tests. In comments I mention limitations due to #20272 and #20285.
Thanks for these!
Code review:
-static int +int networkstatus_compute_bw_weights_v10(smartlist_t *chunks, int64_t G,
should replace static with STATIC. STATIC means "static when building tor, but available when building unit tests".
Otherwise this looks good.
teor: you mention it would be nice to have a test with values from a recent consensus. I agree. Where can I find recent real input values
M
,G
, etc. that went into producingWxx
values? Will an authority need to be nice and share a line from his log with us?
That might be the easiest way - we could ask arma, who runs a recent directory authority, often at detailed log levels. Or we could write a script that downloads a consensus and does that calculation manually. Asking arma might be easier!
comment:46 follow-up: 47 Changed 3 years ago by
Sure. What log lines would you like?
moria1 is currently outputting lines like
Oct 04 18:55:01.567 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29322240 M=4721546 E=1522058 D=9273571 T=44839415
comment:47 Changed 3 years ago by
Replying to arma:
Sure. What log lines would you like?
moria1 is currently outputting lines like
[...] Case 3a (E scarce) with v10: [...]
Lines exactly like that, thanks!
I bet Tor usually sticks with the same Case for long periods of time, but for the sake of variety, could you do a quick search for other Cases in recent history?
comment:48 Changed 3 years ago by
Here you go:
Sep 22 21:55:01.524 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29203290 M=4549813 E=1297342 D=9238190 T=44288635 Sep 22 21:55:01.756 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29203290 M=4549813 E=1297342 D=9238190 T=44288635 Sep 22 22:55:01.603 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29256210 M=4496382 E=1294965 D=9243530 T=44291087 Sep 22 22:55:01.841 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29256210 M=4496382 E=1294965 D=9243530 T=44291087 Sep 22 23:55:01.502 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29295220 M=4441890 E=1270753 D=9209290 T=44217153 Sep 22 23:55:01.716 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29295220 M=4441890 E=1270753 D=9209290 T=44217153 Sep 23 00:55:01.571 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29340940 M=4569705 E=1357328 D=9297810 T=44565783 Sep 23 00:55:01.785 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29340940 M=4569705 E=1357328 D=9297810 T=44565783 Sep 23 01:55:01.508 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29371910 M=4531469 E=1360359 D=9310870 T=44574608 Sep 23 01:55:01.724 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29371910 M=4531469 E=1360359 D=9310870 T=44574608 Sep 23 02:55:01.593 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29270750 M=4509242 E=1365297 D=9303970 T=44449259 Sep 23 02:55:01.804 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29270750 M=4509242 E=1365297 D=9303970 T=44449259 Sep 23 03:55:01.601 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29314870 M=4466842 E=1368374 D=9237310 T=44387396 Sep 23 03:55:01.814 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29314870 M=4466842 E=1368374 D=9237310 T=44387396 Sep 23 04:55:01.541 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29316470 M=4374086 E=1327032 D=9270000 T=44287588 Sep 23 04:55:01.771 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29316470 M=4374086 E=1327032 D=9270000 T=44287588 Sep 23 05:55:01.614 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29316780 M=4390302 E=1348871 D=9285860 T=44341813 Sep 23 05:55:01.828 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29316780 M=4390302 E=1348871 D=9285860 T=44341813 Sep 23 06:55:01.629 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29371270 M=4444339 E=1335815 D=9306940 T=44458364 Sep 23 06:55:01.846 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29371270 M=4444339 E=1335815 D=9306940 T=44458364 Sep 23 07:55:01.598 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29384260 M=4385343 E=1338573 D=9324090 T=44432266 Sep 23 07:55:01.829 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29384260 M=4385343 E=1338573 D=9324090 T=44432266 Sep 23 08:55:01.608 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29404200 M=4369584 E=1321205 D=9282310 T=44377299 Sep 23 08:55:01.831 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29404200 M=4369584 E=1321205 D=9282310 T=44377299 Sep 23 09:55:01.660 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29483510 M=4341154 E=1343763 D=9230060 T=44398487 Sep 23 09:55:01.887 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29483510 M=4341154 E=1343763 D=9230060 T=44398487 Sep 23 10:55:01.644 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29381530 M=4376122 E=1336813 D=9271440 T=44365905 Sep 23 10:55:01.875 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29381530 M=4376122 E=1336813 D=9271440 T=44365905 Sep 23 11:55:01.639 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29368410 M=4364243 E=1320829 D=9284700 T=44338182 Sep 23 11:55:01.890 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29368410 M=4364243 E=1320829 D=9284700 T=44338182 Sep 23 12:55:01.613 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29339900 M=4367583 E=1347978 D=9286460 T=44341921 Sep 23 12:55:01.831 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29339900 M=4367583 E=1347978 D=9286460 T=44341921 Sep 23 13:55:01.510 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29325450 M=4353028 E=1351993 D=9270840 T=44301311 Sep 23 13:55:01.734 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29325450 M=4353028 E=1351993 D=9270840 T=44301311 Sep 23 14:55:01.649 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29179290 M=4308857 E=1356907 D=9244870 T=44089924 Sep 23 14:55:01.871 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29179290 M=4308857 E=1356907 D=9244870 T=44089924 Sep 23 15:55:01.509 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29141380 M=4291615 E=1361438 D=9245960 T=44040393 Sep 23 15:55:01.722 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29141380 M=4291615 E=1361438 D=9245960 T=44040393 Sep 23 16:55:01.527 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29174390 M=4227444 E=1412134 D=9238620 T=44052588 Sep 23 16:55:01.747 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29174390 M=4227444 E=1412134 D=9238620 T=44052588 Sep 23 17:55:01.640 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29146010 M=4175793 E=1461601 D=9228580 T=44011984 Sep 23 17:55:01.882 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29146010 M=4175793 E=1461601 D=9228580 T=44011984 Sep 23 18:55:01.660 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159460 M=4348021 E=1451811 D=9237140 T=44196432 Sep 23 18:55:01.891 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159460 M=4348021 E=1451811 D=9237140 T=44196432 Sep 23 19:55:01.620 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29178730 M=4418242 E=1388923 D=9237390 T=44223285 Sep 23 19:55:01.848 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29178730 M=4418242 E=1388923 D=9237390 T=44223285 Sep 23 20:55:01.517 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29197780 M=4575553 E=1400024 D=9235130 T=44408487 Sep 23 20:55:01.747 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29197780 M=4575553 E=1400024 D=9235130 T=44408487 Sep 23 21:55:01.620 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29220070 M=4569189 E=1411229 D=9261310 T=44461798 Sep 23 21:55:01.858 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29220070 M=4569189 E=1411229 D=9261310 T=44461798 Sep 23 22:55:01.639 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28886480 M=4546573 E=1299735 D=9172330 T=43905118 Sep 23 22:55:01.863 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28886480 M=4546573 E=1299735 D=9172330 T=43905118 Sep 23 23:55:01.500 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29175300 M=4515431 E=1381195 D=9296160 T=44368086 Sep 23 23:55:01.727 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29175300 M=4515431 E=1381195 D=9296160 T=44368086 Sep 24 00:55:01.515 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29156600 M=4579717 E=1371385 D=9320290 T=44427992 Sep 24 00:55:01.754 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29156600 M=4579717 E=1371385 D=9320290 T=44427992 Sep 24 01:55:01.511 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29183340 M=4534903 E=1364382 D=9323660 T=44406285 Sep 24 01:55:01.739 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29183340 M=4534903 E=1364382 D=9323660 T=44406285 Sep 24 02:55:01.584 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159010 M=4489358 E=1349768 D=9327170 T=44325306 Sep 24 02:55:01.817 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159010 M=4489358 E=1349768 D=9327170 T=44325306 Sep 24 03:55:01.517 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29189000 M=4524768 E=1341352 D=9329850 T=44384970 Sep 24 03:55:01.757 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29189000 M=4524768 E=1341352 D=9329850 T=44384970 Sep 24 04:55:01.517 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29171950 M=4465246 E=1341338 D=9303430 T=44281964 Sep 24 04:55:01.737 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29171950 M=4465246 E=1341338 D=9303430 T=44281964 Sep 24 05:55:01.579 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29101890 M=4507268 E=1342452 D=9323040 T=44274650 Sep 24 05:55:01.810 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29101890 M=4507268 E=1342452 D=9323040 T=44274650 Sep 24 06:55:01.498 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29141550 M=4498769 E=1354065 D=9315460 T=44309844 Sep 24 06:55:01.716 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29141550 M=4498769 E=1354065 D=9315460 T=44309844 Sep 24 07:55:01.537 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29083550 M=4338581 E=1467704 D=9259540 T=44149375 Sep 24 07:55:01.762 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29083550 M=4338581 E=1467704 D=9259540 T=44149375 Sep 24 08:55:01.603 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29146280 M=4318826 E=1465617 D=9250430 T=44181153 Sep 24 08:55:01.822 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29146280 M=4318826 E=1465617 D=9250430 T=44181153 Sep 24 09:55:01.622 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29155890 M=4330784 E=1466951 D=9228070 T=44181695 Sep 24 09:55:01.860 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29155890 M=4330784 E=1466951 D=9228070 T=44181695 Sep 24 10:55:01.597 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29099570 M=4296361 E=1458662 D=9260900 T=44115493 Sep 24 10:55:01.840 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29099570 M=4296361 E=1458662 D=9260900 T=44115493 Sep 24 11:55:01.645 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29109260 M=4260399 E=1416494 D=9281640 T=44067793 Sep 24 11:55:01.871 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29109260 M=4260399 E=1416494 D=9281640 T=44067793 Sep 24 12:55:01.556 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29128920 M=4233724 E=1423206 D=9264520 T=44050370 Sep 24 12:55:01.782 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29128920 M=4233724 E=1423206 D=9264520 T=44050370 Sep 24 13:55:01.532 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29030640 M=4164810 E=1349037 D=9181310 T=43725797 Sep 24 13:55:01.755 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29030640 M=4164810 E=1349037 D=9181310 T=43725797 Sep 24 14:55:01.517 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29062130 M=4138229 E=1369929 D=9188880 T=43759168 Sep 24 14:55:01.752 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29062130 M=4138229 E=1369929 D=9188880 T=43759168 Sep 24 15:55:01.505 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29043290 M=4102735 E=1371991 D=9180530 T=43698546 Sep 24 15:55:01.722 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29043290 M=4102735 E=1371991 D=9180530 T=43698546 Sep 24 16:55:01.648 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28760090 M=4327349 E=1426867 D=9130990 T=43645296 Sep 24 16:55:01.894 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28760090 M=4327349 E=1426867 D=9130990 T=43645296 Sep 24 17:55:01.777 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28780640 M=4300174 E=1475051 D=9110740 T=43666605 Sep 24 17:55:02.026 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28780640 M=4300174 E=1475051 D=9110740 T=43666605 Sep 24 18:55:01.702 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28793720 M=4370117 E=1500636 D=9092340 T=43756813 Sep 24 18:55:01.938 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28793720 M=4370117 E=1500636 D=9092340 T=43756813 Sep 24 19:55:01.639 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28809740 M=4395161 E=1458988 D=9083600 T=43747489 Sep 24 19:55:01.881 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28809740 M=4395161 E=1458988 D=9083600 T=43747489 Sep 24 20:55:01.612 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28807270 M=4570971 E=1462077 D=9092470 T=43932788 Sep 24 20:55:01.859 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28807270 M=4570971 E=1462077 D=9092470 T=43932788 Sep 24 21:55:01.752 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28810500 M=4549659 E=1476268 D=9087090 T=43923517 Sep 24 21:55:02.007 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28810500 M=4549659 E=1476268 D=9087090 T=43923517 Sep 24 22:55:01.557 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28784310 M=4584870 E=1461745 D=9108200 T=43939125 Sep 24 22:55:01.812 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28784310 M=4584870 E=1461745 D=9108200 T=43939125 Sep 24 23:55:01.661 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28836790 M=4512825 E=1469571 D=9114380 T=43933566 Sep 24 23:55:01.923 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28836790 M=4512825 E=1469571 D=9114380 T=43933566 Sep 25 00:55:01.744 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28843910 M=4584267 E=1476627 D=9140320 T=44045124 Sep 25 00:55:01.985 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28843910 M=4584267 E=1476627 D=9140320 T=44045124 Sep 25 01:55:01.663 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28885550 M=4595701 E=1465882 D=9153370 T=44100503 Sep 25 01:55:01.910 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28885550 M=4595701 E=1465882 D=9153370 T=44100503 Sep 25 02:55:01.753 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28868190 M=4609469 E=1469019 D=9157150 T=44103828 Sep 25 02:55:01.997 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28868190 M=4609469 E=1469019 D=9157150 T=44103828 Sep 25 03:55:01.622 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28908270 M=4576901 E=1508946 D=9158260 T=44152377 Sep 25 03:55:01.892 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28908270 M=4576901 E=1508946 D=9158260 T=44152377 Sep 25 04:55:01.779 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28929810 M=4527217 E=1495740 D=9239540 T=44192307 Sep 25 04:55:02.016 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28929810 M=4527217 E=1495740 D=9239540 T=44192307 Sep 25 05:55:01.648 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28922580 M=4418268 E=1483602 D=9248580 T=44073030 Sep 25 05:55:01.897 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28922580 M=4418268 E=1483602 D=9248580 T=44073030 Sep 25 06:55:01.794 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28926900 M=4460126 E=1500885 D=9248210 T=44136121 Sep 25 06:55:02.033 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28926900 M=4460126 E=1500885 D=9248210 T=44136121 Sep 25 07:55:01.804 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28898010 M=4461828 E=1512974 D=9246570 T=44119382 Sep 25 07:55:02.046 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28898010 M=4461828 E=1512974 D=9246570 T=44119382 Sep 25 08:55:01.730 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28874610 M=4417891 E=1465144 D=9261970 T=44019615 Sep 25 08:55:01.986 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28874610 M=4417891 E=1465144 D=9261970 T=44019615 Sep 25 09:55:01.746 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28952000 M=4359811 E=1495023 D=9259800 T=44066634 Sep 25 09:55:02.003 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28952000 M=4359811 E=1495023 D=9259800 T=44066634 Sep 25 10:55:01.816 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28956370 M=4329503 E=1509739 D=9260760 T=44056372 Sep 25 10:55:02.070 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28956370 M=4329503 E=1509739 D=9260760 T=44056372 Sep 25 11:55:01.863 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28951090 M=4315616 E=1500555 D=9218620 T=43985881 Sep 25 11:55:02.125 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28951090 M=4315616 E=1500555 D=9218620 T=43985881 Sep 25 12:55:01.720 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28972990 M=4285405 E=1504141 D=9225190 T=43987726 Sep 25 12:55:01.961 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28972990 M=4285405 E=1504141 D=9225190 T=43987726 Sep 25 13:55:01.816 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28834970 M=4218541 E=1497621 D=9146280 T=43697412 Sep 25 13:55:02.055 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28834970 M=4218541 E=1497621 D=9146280 T=43697412 Sep 25 14:55:01.833 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28837720 M=4240528 E=1486179 D=9163530 T=43727957 Sep 25 14:55:02.077 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28837720 M=4240528 E=1486179 D=9163530 T=43727957 Sep 25 15:55:01.833 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28740982 M=4236792 E=1528404 D=9164410 T=43670588 Sep 25 15:55:02.077 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28740982 M=4236792 E=1528404 D=9164410 T=43670588 Sep 25 16:55:01.796 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28859673 M=4198594 E=1525791 D=9148950 T=43733008 Sep 25 16:55:02.036 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28859673 M=4198594 E=1525791 D=9148950 T=43733008 Sep 25 17:55:01.890 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28648238 M=4210277 E=1582228 D=9115990 T=43556733 Sep 25 17:55:02.128 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28648238 M=4210277 E=1582228 D=9115990 T=43556733 Sep 25 18:55:01.874 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28658178 M=4349187 E=1592737 D=9125149 T=43725251 Sep 25 18:55:02.112 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28658178 M=4349187 E=1592737 D=9125149 T=43725251 Sep 25 19:55:01.732 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28689158 M=4324985 E=1508524 D=9139779 T=43662446 Sep 25 19:55:01.989 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28689158 M=4324985 E=1508524 D=9139779 T=43662446 Sep 25 20:55:01.832 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28792529 M=4509638 E=1502240 D=9160369 T=43964776 Sep 25 20:55:02.085 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28792529 M=4509638 E=1502240 D=9160369 T=43964776 Sep 25 21:55:01.895 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28804388 M=4520570 E=1507519 D=9176289 T=44008766 Sep 25 21:55:02.167 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28804388 M=4520570 E=1507519 D=9176289 T=44008766 Sep 25 22:55:01.917 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28892326 M=4569795 E=1495627 D=9213159 T=44170907 Sep 25 22:55:02.164 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28892326 M=4569795 E=1495627 D=9213159 T=44170907 Sep 25 23:55:01.894 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28925403 M=4531304 E=1482610 D=9235260 T=44174577 Sep 25 23:55:02.139 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28925403 M=4531304 E=1482610 D=9235260 T=44174577 Sep 26 00:55:01.938 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28962550 M=4638024 E=1483258 D=9228570 T=44312402 Sep 26 00:55:02.190 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28962550 M=4638024 E=1483258 D=9228570 T=44312402 Sep 26 01:55:01.904 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29026503 M=4673839 E=1490685 D=9252390 T=44443417 Sep 26 01:55:02.155 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29026503 M=4673839 E=1490685 D=9252390 T=44443417 Sep 26 02:55:01.821 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29030152 M=4634618 E=1415181 D=9257370 T=44337321 Sep 26 02:55:02.085 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29030152 M=4634618 E=1415181 D=9257370 T=44337321 Sep 26 03:55:01.947 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29096165 M=4597031 E=1399581 D=9327680 T=44420457 Sep 26 03:55:02.186 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29096165 M=4597031 E=1399581 D=9327680 T=44420457 Sep 26 04:55:01.919 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29125773 M=4537906 E=1372263 D=9333930 T=44369872 Sep 26 04:55:02.163 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29125773 M=4537906 E=1372263 D=9333930 T=44369872 Sep 26 05:55:01.941 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29117856 M=4495833 E=1492737 D=9326950 T=44433376 Sep 26 05:55:02.211 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29117856 M=4495833 E=1492737 D=9326950 T=44433376 Sep 26 06:55:01.858 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29104136 M=4445099 E=1513797 D=9320530 T=44383562 Sep 26 06:55:02.100 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29104136 M=4445099 E=1513797 D=9320530 T=44383562 Sep 26 07:55:01.898 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29091206 M=4421333 E=1486975 D=9314210 T=44313724 Sep 26 07:55:02.140 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29091206 M=4421333 E=1486975 D=9314210 T=44313724 Sep 26 08:55:01.909 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29127776 M=4386028 E=1483310 D=9314460 T=44311574 Sep 26 08:55:02.148 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29127776 M=4386028 E=1483310 D=9314460 T=44311574 Sep 26 09:55:02.021 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29093186 M=4381929 E=1501679 D=9309660 T=44286454 Sep 26 09:55:02.264 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29093186 M=4381929 E=1501679 D=9309660 T=44286454 Sep 26 10:55:01.847 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29046056 M=4339967 E=1487182 D=9320350 T=44193555 Sep 26 10:55:02.093 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29046056 M=4339967 E=1487182 D=9320350 T=44193555 Sep 26 11:55:01.846 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29048206 M=4354198 E=1473272 D=9302310 T=44177986 Sep 26 11:55:02.084 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29048206 M=4354198 E=1473272 D=9302310 T=44177986 Sep 26 12:55:01.910 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29090316 M=4345354 E=1483634 D=9275160 T=44194464 Sep 26 12:55:02.153 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29090316 M=4345354 E=1483634 D=9275160 T=44194464 Sep 26 13:55:01.826 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29089017 M=4259495 E=1478294 D=9274310 T=44101116 Sep 26 13:55:02.062 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29089017 M=4259495 E=1478294 D=9274310 T=44101116 Sep 26 14:55:01.825 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28964007 M=4253230 E=1458324 D=9270190 T=43945751 Sep 26 14:55:02.062 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28964007 M=4253230 E=1458324 D=9270190 T=43945751 Sep 26 15:55:01.721 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28928467 M=4237529 E=1448971 D=9205430 T=43820397 Sep 26 15:55:01.959 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28928467 M=4237529 E=1448971 D=9205430 T=43820397 Sep 26 16:55:01.848 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28971497 M=4198876 E=1423897 D=9205910 T=43800180 Sep 26 16:55:02.092 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28971497 M=4198876 E=1423897 D=9205910 T=43800180 Sep 26 17:55:01.924 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28980077 M=4170538 E=1503233 D=9249010 T=43902858 Sep 26 17:55:02.167 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28980077 M=4170538 E=1503233 D=9249010 T=43902858 Sep 26 18:55:01.936 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28915707 M=4277846 E=1480540 D=9080180 T=43754273 Sep 26 18:55:02.180 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28915707 M=4277846 E=1480540 D=9080180 T=43754273 Sep 26 19:55:01.832 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28923901 M=4314943 E=1421018 D=9055930 T=43715792 Sep 26 19:55:02.073 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28923901 M=4314943 E=1421018 D=9055930 T=43715792 Sep 26 20:55:01.876 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28869671 M=4516673 E=1420049 D=9087220 T=43893613 Sep 26 20:55:02.114 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28869671 M=4516673 E=1420049 D=9087220 T=43893613 Sep 26 21:55:01.933 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28960861 M=4449809 E=1424295 D=9132490 T=43967455 Sep 26 21:55:02.189 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28960861 M=4449809 E=1424295 D=9132490 T=43967455 Sep 26 22:55:01.894 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29136521 M=4446064 E=1414681 D=9115040 T=44112306 Sep 26 22:55:02.126 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29136521 M=4446064 E=1414681 D=9115040 T=44112306 Sep 26 23:55:02.000 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29139931 M=4458914 E=1439430 D=9085810 T=44124085 Sep 26 23:55:02.240 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29139931 M=4458914 E=1439430 D=9085810 T=44124085 Sep 27 00:55:01.903 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29110861 M=4531193 E=1431239 D=9062650 T=44135943 Sep 27 00:55:02.152 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29110861 M=4531193 E=1431239 D=9062650 T=44135943 Sep 27 01:55:02.036 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29099501 M=4513792 E=1423931 D=9038150 T=44075374 Sep 27 01:55:02.279 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29099501 M=4513792 E=1423931 D=9038150 T=44075374 Sep 27 02:55:01.822 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29198481 M=4486894 E=1442188 D=9110110 T=44237673 Sep 27 02:55:02.063 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29198481 M=4486894 E=1442188 D=9110110 T=44237673 Sep 27 03:55:01.907 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29239191 M=4497044 E=1421002 D=9138470 T=44295707 Sep 27 03:55:02.152 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29239191 M=4497044 E=1421002 D=9138470 T=44295707 Sep 27 04:55:01.917 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29203141 M=4447784 E=1433859 D=9150520 T=44235304 Sep 27 04:55:02.155 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29203141 M=4447784 E=1433859 D=9150520 T=44235304 Sep 27 05:55:01.843 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29201171 M=4423498 E=1434312 D=9137960 T=44196941 Sep 27 05:55:02.084 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29201171 M=4423498 E=1434312 D=9137960 T=44196941 Sep 27 06:55:01.858 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29179171 M=4336223 E=1434331 D=9133580 T=44083305 Sep 27 06:55:02.105 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29179171 M=4336223 E=1434331 D=9133580 T=44083305 Sep 27 07:55:01.938 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29157606 M=4311416 E=1409118 D=9142790 T=44020930 Sep 27 07:55:02.191 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29157606 M=4311416 E=1409118 D=9142790 T=44020930 Sep 27 08:55:01.818 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29116336 M=4254537 E=1409593 D=9125070 T=43905536 Sep 27 08:55:02.071 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29116336 M=4254537 E=1409593 D=9125070 T=43905536 Sep 27 09:55:01.903 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29158716 M=4233850 E=1416868 D=9117050 T=43926484 Sep 27 09:55:02.142 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29158716 M=4233850 E=1416868 D=9117050 T=43926484 Sep 27 10:55:01.811 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29045381 M=4220188 E=1415009 D=9066660 T=43747238 Sep 27 10:55:02.058 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29045381 M=4220188 E=1415009 D=9066660 T=43747238 Sep 27 11:55:01.934 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29130501 M=4207655 E=1437215 D=9066570 T=43841941 Sep 27 11:55:02.179 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29130501 M=4207655 E=1437215 D=9066570 T=43841941 Sep 27 12:55:01.905 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29065791 M=4257934 E=1441633 D=9077350 T=43842708 Sep 27 12:55:02.147 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29065791 M=4257934 E=1441633 D=9077350 T=43842708 Sep 27 13:55:01.698 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29211681 M=4127733 E=1396760 D=9104480 T=43840654 Sep 27 13:55:01.924 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29211681 M=4127733 E=1396760 D=9104480 T=43840654 Sep 27 14:55:01.783 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29172341 M=4060757 E=1412745 D=9063830 T=43709673 Sep 27 14:55:02.005 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29172341 M=4060757 E=1412745 D=9063830 T=43709673 Sep 27 15:55:01.713 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29062251 M=4048690 E=1420324 D=9057550 T=43588815 Sep 27 15:55:01.944 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29062251 M=4048690 E=1420324 D=9057550 T=43588815 Sep 27 16:55:01.795 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29071331 M=4033376 E=1432461 D=9041340 T=43578508 Sep 27 16:55:02.018 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29071331 M=4033376 E=1432461 D=9041340 T=43578508 Sep 27 17:55:01.720 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29046411 M=4015860 E=1486073 D=8931600 T=43479944 Sep 27 17:55:01.952 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29046411 M=4015860 E=1486073 D=8931600 T=43479944 Sep 27 18:55:01.712 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29028421 M=4163557 E=1519939 D=9022300 T=43734217 Sep 27 18:55:01.961 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29028421 M=4163557 E=1519939 D=9022300 T=43734217 Sep 27 19:55:01.813 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29019210 M=4185713 E=1477182 D=9037710 T=43719815 Sep 27 19:55:02.047 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29019210 M=4185713 E=1477182 D=9037710 T=43719815 Sep 27 20:55:01.668 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29037730 M=4420138 E=1485581 D=9057550 T=44000999 Sep 27 20:55:01.888 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29037730 M=4420138 E=1485581 D=9057550 T=44000999 Sep 27 21:55:01.823 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29092120 M=4474098 E=1490565 D=9215380 T=44272163 Sep 27 21:55:02.089 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29092120 M=4474098 E=1490565 D=9215380 T=44272163 Sep 27 22:55:01.805 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29092350 M=4515258 E=1491664 D=9229960 T=44329232 Sep 27 22:55:02.035 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29092350 M=4515258 E=1491664 D=9229960 T=44329232 Sep 27 23:55:01.730 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29102610 M=4522023 E=1483517 D=9248010 T=44356160 Sep 27 23:55:01.972 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29102610 M=4522023 E=1483517 D=9248010 T=44356160 Sep 28 00:55:01.710 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29178940 M=4551956 E=1487002 D=9243530 T=44461428 Sep 28 00:55:01.935 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29178940 M=4551956 E=1487002 D=9243530 T=44461428 Sep 28 01:55:01.721 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29132910 M=4524250 E=1482207 D=9273300 T=44412667 Sep 28 01:55:01.947 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29132910 M=4524250 E=1482207 D=9273300 T=44412667 Sep 28 02:55:02.067 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29016540 M=4593146 E=1552979 D=9213090 T=44375755 Sep 28 02:55:02.306 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29016540 M=4593146 E=1552979 D=9213090 T=44375755 Sep 28 03:55:01.937 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29011820 M=4657562 E=1509013 D=9215390 T=44393785 Sep 28 03:55:02.177 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29011820 M=4657562 E=1509013 D=9215390 T=44393785 Sep 28 04:55:01.851 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29017000 M=4643609 E=1533795 D=9243710 T=44438114 Sep 28 04:55:02.108 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29017000 M=4643609 E=1533795 D=9243710 T=44438114 Sep 28 05:55:02.044 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29057500 M=4624030 E=1547208 D=9246980 T=44475718 Sep 28 05:55:02.284 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29057500 M=4624030 E=1547208 D=9246980 T=44475718 Sep 28 06:55:01.883 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29028940 M=4542626 E=1567128 D=9231750 T=44370444 Sep 28 06:55:02.120 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29028940 M=4542626 E=1567128 D=9231750 T=44370444 Sep 28 07:55:02.003 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28931270 M=4500708 E=1530957 D=9244930 T=44207865 Sep 28 07:55:02.234 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28931270 M=4500708 E=1530957 D=9244930 T=44207865 Sep 28 08:55:01.996 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28932210 M=4459812 E=1526403 D=9241900 T=44160325 Sep 28 08:55:02.225 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28932210 M=4459812 E=1526403 D=9241900 T=44160325 Sep 28 09:55:01.791 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29100920 M=4311095 E=1535542 D=9253930 T=44201487 Sep 28 09:55:02.024 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29100920 M=4311095 E=1535542 D=9253930 T=44201487 Sep 28 10:55:01.824 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29136330 M=4303000 E=1518397 D=9247730 T=44205457 Sep 28 10:55:02.057 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29136330 M=4303000 E=1518397 D=9247730 T=44205457 Sep 28 11:55:01.972 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29172440 M=4228516 E=1525113 D=9242710 T=44168779 Sep 28 11:55:02.201 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29172440 M=4228516 E=1525113 D=9242710 T=44168779 Sep 28 12:55:01.247 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29188950 M=4334946 E=1502389 D=9266650 T=44292935 Sep 28 12:55:01.481 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29188950 M=4334946 E=1502389 D=9266650 T=44292935 Sep 28 13:55:01.428 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29121348 M=4297605 E=1522631 D=9266650 T=44208234 Sep 28 13:55:01.657 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29121348 M=4297605 E=1522631 D=9266650 T=44208234 Sep 28 14:55:01.345 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28982358 M=4296010 E=1512526 D=9258930 T=44049824 Sep 28 14:55:01.586 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28982358 M=4296010 E=1512526 D=9258930 T=44049824 Sep 28 15:55:01.362 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28908398 M=4310653 E=1556174 D=9246020 T=44021245 Sep 28 15:55:01.591 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28908398 M=4310653 E=1556174 D=9246020 T=44021245 Sep 28 16:55:01.431 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28957348 M=4274284 E=1543733 D=9251670 T=44027035 Sep 28 16:55:01.661 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28957348 M=4274284 E=1543733 D=9251670 T=44027035 Sep 28 17:55:01.256 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28949798 M=4274205 E=1613125 D=9240000 T=44077128 Sep 28 17:55:01.488 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28949798 M=4274205 E=1613125 D=9240000 T=44077128 Sep 28 18:55:01.246 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28929228 M=4418717 E=1646195 D=9228980 T=44223120 Sep 28 18:55:01.478 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28929228 M=4418717 E=1646195 D=9228980 T=44223120 Sep 28 19:55:01.485 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28939738 M=4456391 E=1555930 D=9215670 T=44167729 Sep 28 19:55:01.719 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28939738 M=4456391 E=1555930 D=9215670 T=44167729 Sep 28 20:55:01.555 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28873808 M=4607283 E=1578402 D=9038140 T=44097633 Sep 28 20:55:01.788 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28873808 M=4607283 E=1578402 D=9038140 T=44097633 Sep 28 21:55:01.305 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28963238 M=4589657 E=1581867 D=9035400 T=44170162 Sep 28 21:55:01.539 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28963238 M=4589657 E=1581867 D=9035400 T=44170162 Sep 28 22:55:01.422 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29086458 M=4602378 E=1572649 D=9067750 T=44329235 Sep 28 22:55:01.652 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29086458 M=4602378 E=1572649 D=9067750 T=44329235 Sep 28 23:55:01.417 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29094188 M=4581631 E=1574678 D=9097850 T=44348347 Sep 28 23:55:01.647 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29094188 M=4581631 E=1574678 D=9097850 T=44348347 Sep 29 00:55:01.466 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29048098 M=4659149 E=1572161 D=9099940 T=44379348 Sep 29 00:55:01.695 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29048098 M=4659149 E=1572161 D=9099940 T=44379348 Sep 29 01:55:01.247 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29040908 M=4670996 E=1562165 D=9113640 T=44387709 Sep 29 01:55:01.477 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29040908 M=4670996 E=1562165 D=9113640 T=44387709 Sep 29 02:55:01.392 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29106588 M=4641857 E=1566358 D=9115100 T=44429903 Sep 29 02:55:01.622 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29106588 M=4641857 E=1566358 D=9115100 T=44429903 Sep 29 03:55:01.439 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29100848 M=4531278 E=1574498 D=9151100 T=44357724 Sep 29 03:55:01.671 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29100848 M=4531278 E=1574498 D=9151100 T=44357724 Sep 29 04:55:01.471 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29114520 M=4506275 E=1551683 D=9151860 T=44324338 Sep 29 04:55:01.703 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29114520 M=4506275 E=1551683 D=9151860 T=44324338 Sep 29 05:55:01.424 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29083400 M=4528733 E=1563302 D=9158480 T=44333915 Sep 29 05:55:01.655 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29083400 M=4528733 E=1563302 D=9158480 T=44333915 Sep 29 06:55:01.358 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29160230 M=4522185 E=1554576 D=9170050 T=44407041 Sep 29 06:55:01.590 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29160230 M=4522185 E=1554576 D=9170050 T=44407041 Sep 29 07:55:01.231 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29220320 M=4470275 E=1548605 D=9187290 T=44426490 Sep 29 07:55:01.464 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29220320 M=4470275 E=1548605 D=9187290 T=44426490 Sep 29 08:55:01.318 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29218810 M=4439650 E=1541648 D=9185960 T=44386068 Sep 29 08:55:01.548 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29218810 M=4439650 E=1541648 D=9185960 T=44386068 Sep 29 09:55:01.400 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29215850 M=4413074 E=1572515 D=9242410 T=44443849 Sep 29 09:55:01.633 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29215850 M=4413074 E=1572515 D=9242410 T=44443849 Sep 29 10:55:01.368 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29123870 M=4372204 E=1589749 D=9185980 T=44271803 Sep 29 10:55:01.600 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29123870 M=4372204 E=1589749 D=9185980 T=44271803 Sep 29 11:55:01.363 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29191200 M=4297243 E=1606487 D=9181800 T=44276730 Sep 29 11:55:01.596 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29191200 M=4297243 E=1606487 D=9181800 T=44276730 Sep 29 12:55:01.456 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29189590 M=4386965 E=1584502 D=9103780 T=44264837 Sep 29 12:55:01.697 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29189590 M=4386965 E=1584502 D=9103780 T=44264837 Sep 29 13:55:01.454 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29197490 M=4330602 E=1581805 D=9080070 T=44189967 Sep 29 13:55:01.684 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29197490 M=4330602 E=1581805 D=9080070 T=44189967 Sep 29 14:55:01.356 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29186530 M=4308505 E=1594796 D=9074970 T=44164801 Sep 29 14:55:01.598 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29186530 M=4308505 E=1594796 D=9074970 T=44164801 Sep 29 15:55:01.359 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29200940 M=4338061 E=1577181 D=9081070 T=44197252 Sep 29 15:55:01.588 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29200940 M=4338061 E=1577181 D=9081070 T=44197252 Sep 29 16:55:01.296 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29222680 M=4357737 E=1475141 D=8813660 T=43869218 Sep 29 16:55:01.531 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29222680 M=4357737 E=1475141 D=8813660 T=43869218 Sep 29 17:55:01.310 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29226170 M=4322405 E=1595815 D=9011140 T=44155530 Sep 29 17:55:01.541 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29226170 M=4322405 E=1595815 D=9011140 T=44155530 Sep 29 18:55:01.456 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29224310 M=4491044 E=1604863 D=9006760 T=44326977 Sep 29 18:55:01.704 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29224310 M=4491044 E=1604863 D=9006760 T=44326977 Sep 29 19:55:01.368 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29204470 M=4507301 E=1528295 D=8995480 T=44235546 Sep 29 19:55:01.598 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29204470 M=4507301 E=1528295 D=8995480 T=44235546 Sep 29 20:55:01.437 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29193450 M=4679351 E=1544294 D=8980680 T=44397775 Sep 29 20:55:01.673 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29193450 M=4679351 E=1544294 D=8980680 T=44397775 Sep 29 21:55:01.308 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29188210 M=4651476 E=1556781 D=8993160 T=44389627 Sep 29 21:55:01.539 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29188210 M=4651476 E=1556781 D=8993160 T=44389627 Sep 29 22:55:01.429 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29116640 M=4667749 E=1539147 D=8939230 T=44262766 Sep 29 22:55:01.662 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29116640 M=4667749 E=1539147 D=8939230 T=44262766 Sep 29 23:55:01.365 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29114670 M=4553443 E=1597119 D=8942570 T=44207802 Sep 29 23:55:01.626 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29114670 M=4553443 E=1597119 D=8942570 T=44207802 Sep 30 00:55:01.406 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159370 M=4613612 E=1596158 D=9041800 T=44410940 Sep 30 00:55:01.640 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159370 M=4613612 E=1596158 D=9041800 T=44410940 Sep 30 01:55:01.562 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29097910 M=4590942 E=1589576 D=9009890 T=44288318 Sep 30 01:55:01.801 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29097910 M=4590942 E=1589576 D=9009890 T=44288318 Sep 30 02:55:01.386 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29091260 M=4682597 E=1609471 D=9048140 T=44431468 Sep 30 02:55:01.716 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29091260 M=4682597 E=1609471 D=9048140 T=44431468 Sep 30 03:55:01.480 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29089800 M=4632350 E=1609144 D=9073300 T=44404594 Sep 30 03:55:01.719 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29089800 M=4632350 E=1609144 D=9073300 T=44404594 Sep 30 04:55:01.459 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29126790 M=4618605 E=1598174 D=9101340 T=44444909 Sep 30 04:55:01.691 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29126790 M=4618605 E=1598174 D=9101340 T=44444909 Sep 30 05:55:01.427 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29101550 M=4569295 E=1592371 D=9105150 T=44368366 Sep 30 05:55:01.667 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29101550 M=4569295 E=1592371 D=9105150 T=44368366 Sep 30 06:55:01.444 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29096420 M=4427788 E=1605960 D=9132220 T=44262388 Sep 30 06:55:01.684 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29096420 M=4427788 E=1605960 D=9132220 T=44262388 Sep 30 07:55:01.362 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28991880 M=4414147 E=1592538 D=9168220 T=44166785 Sep 30 07:55:01.594 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28991880 M=4414147 E=1592538 D=9168220 T=44166785 Sep 30 08:55:01.429 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28977510 M=4356521 E=1590377 D=9173491 T=44097899 Sep 30 08:55:01.667 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28977510 M=4356521 E=1590377 D=9173491 T=44097899 Sep 30 09:55:01.381 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29007860 M=4418298 E=1573732 D=9148541 T=44148431 Sep 30 09:55:01.624 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29007860 M=4418298 E=1573732 D=9148541 T=44148431 Sep 30 10:55:01.444 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29060820 M=4401288 E=1570117 D=9146671 T=44178896 Sep 30 10:55:01.683 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29060820 M=4401288 E=1570117 D=9146671 T=44178896 Sep 30 11:55:01.245 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29111490 M=4392371 E=1575705 D=9129211 T=44208777 Sep 30 11:55:01.492 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29111490 M=4392371 E=1575705 D=9129211 T=44208777 Sep 30 12:55:01.384 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29078600 M=4419525 E=1580924 D=9152361 T=44231410 Sep 30 12:55:01.644 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29078600 M=4419525 E=1580924 D=9152361 T=44231410 Sep 30 13:55:01.436 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29070110 M=4432569 E=1435411 D=9322531 T=44260621 Sep 30 13:55:01.674 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29070110 M=4432569 E=1435411 D=9322531 T=44260621 Sep 30 14:55:01.418 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29061670 M=4436118 E=1436641 D=9327221 T=44261650 Sep 30 14:55:01.670 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29061670 M=4436118 E=1436641 D=9327221 T=44261650 Sep 30 15:55:01.389 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29067350 M=4350915 E=1465108 D=9323191 T=44206564 Sep 30 15:55:01.639 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29067350 M=4350915 E=1465108 D=9323191 T=44206564 Sep 30 16:55:01.324 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29033900 M=4285802 E=1459010 D=9317711 T=44096423 Sep 30 16:55:01.577 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29033900 M=4285802 E=1459010 D=9317711 T=44096423 Sep 30 17:55:01.475 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29080090 M=4197202 E=1532054 D=9269900 T=44079246 Sep 30 17:55:01.741 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29080090 M=4197202 E=1532054 D=9269900 T=44079246 Sep 30 18:55:01.472 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29089970 M=4422852 E=1563590 D=9258720 T=44335132 Sep 30 18:55:01.724 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29089970 M=4422852 E=1563590 D=9258720 T=44335132 Sep 30 19:55:01.381 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29126780 M=4457433 E=1515479 D=9276530 T=44376222 Sep 30 19:55:01.630 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29126780 M=4457433 E=1515479 D=9276530 T=44376222 Sep 30 20:55:01.437 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29006490 M=4758303 E=1544735 D=9245950 T=44555478 Sep 30 20:55:01.686 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29006490 M=4758303 E=1544735 D=9245950 T=44555478 Sep 30 21:55:01.397 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29002540 M=4741115 E=1552147 D=9228280 T=44524082 Sep 30 21:55:01.640 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29002540 M=4741115 E=1552147 D=9228280 T=44524082 Sep 30 22:55:01.466 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29041690 M=4704082 E=1618555 D=9186090 T=44550417 Sep 30 22:55:01.710 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29041690 M=4704082 E=1618555 D=9186090 T=44550417 Sep 30 23:55:01.530 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29082690 M=4649644 E=1621463 D=9216290 T=44570087 Sep 30 23:55:01.763 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29082690 M=4649644 E=1621463 D=9216290 T=44570087 Oct 01 00:55:01.497 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29035920 M=4748298 E=1620345 D=9306690 T=44711253 Oct 01 00:55:01.750 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29035920 M=4748298 E=1620345 D=9306690 T=44711253 Oct 01 01:55:01.532 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29071430 M=4732182 E=1613506 D=9313460 T=44730578 Oct 01 01:55:01.771 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29071430 M=4732182 E=1613506 D=9313460 T=44730578 Oct 01 02:55:01.451 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28980180 M=4712506 E=1589996 D=9302230 T=44584912 Oct 01 02:55:01.693 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28980180 M=4712506 E=1589996 D=9302230 T=44584912 Oct 01 03:55:01.499 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29038570 M=4689356 E=1589104 D=9311010 T=44628040 Oct 01 03:55:01.750 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29038570 M=4689356 E=1589104 D=9311010 T=44628040 Oct 01 04:55:01.377 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29011680 M=4643509 E=1567511 D=9313260 T=44535960 Oct 01 04:55:01.615 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29011680 M=4643509 E=1567511 D=9313260 T=44535960 Oct 01 05:55:01.523 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28964410 M=4682557 E=1558433 D=9350070 T=44555470 Oct 01 05:55:01.770 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28964410 M=4682557 E=1558433 D=9350070 T=44555470 Oct 01 06:55:01.547 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29042900 M=4625974 E=1554591 D=9350860 T=44574325 Oct 01 06:55:01.791 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29042900 M=4625974 E=1554591 D=9350860 T=44574325 Oct 01 07:55:01.522 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28978670 M=4590290 E=1571828 D=9358100 T=44498888 Oct 01 07:55:01.755 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28978670 M=4590290 E=1571828 D=9358100 T=44498888 Oct 01 08:55:01.392 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29004670 M=4538379 E=1588073 D=9364920 T=44496042 Oct 01 08:55:01.635 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29004670 M=4538379 E=1588073 D=9364920 T=44496042 Oct 01 09:55:01.649 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28915770 M=4514323 E=1562685 D=9385730 T=44378508 Oct 01 09:55:01.897 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28915770 M=4514323 E=1562685 D=9385730 T=44378508 Oct 01 10:55:01.522 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28981410 M=4477070 E=1541711 D=9426890 T=44427081 Oct 01 10:55:01.766 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28981410 M=4477070 E=1541711 D=9426890 T=44427081 Oct 01 11:55:01.552 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28952120 M=4420379 E=1557323 D=9439670 T=44369492 Oct 01 11:55:01.809 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28952120 M=4420379 E=1557323 D=9439670 T=44369492 Oct 01 12:55:01.657 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29022740 M=4465834 E=1550763 D=9436660 T=44475997 Oct 01 12:55:01.926 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29022740 M=4465834 E=1550763 D=9436660 T=44475997 Oct 01 13:55:01.602 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29051460 M=4454516 E=1562727 D=9428050 T=44496753 Oct 01 13:55:01.859 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29051460 M=4454516 E=1562727 D=9428050 T=44496753 Oct 01 14:55:01.653 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29036530 M=4436197 E=1573040 D=9400770 T=44446537 Oct 01 14:55:01.910 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29036530 M=4436197 E=1573040 D=9400770 T=44446537 Oct 01 15:55:01.614 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29021790 M=4446621 E=1542213 D=9374520 T=44385144 Oct 01 15:55:01.863 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29021790 M=4446621 E=1542213 D=9374520 T=44385144 Oct 01 16:55:01.495 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29014590 M=4449086 E=1528100 D=9376690 T=44368466 Oct 01 16:55:01.737 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29014590 M=4449086 E=1528100 D=9376690 T=44368466 Oct 01 17:55:01.532 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28969780 M=4461727 E=1606700 D=9372190 T=44410397 Oct 01 17:55:01.769 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28969780 M=4461727 E=1606700 D=9372190 T=44410397 Oct 01 18:55:01.641 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28991120 M=4585411 E=1613392 D=9388980 T=44578903 Oct 01 18:55:01.890 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28991120 M=4585411 E=1613392 D=9388980 T=44578903 Oct 01 19:55:01.492 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28940350 M=4567587 E=1541470 D=9334940 T=44384347 Oct 01 19:55:01.774 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28940350 M=4567587 E=1541470 D=9334940 T=44384347 Oct 01 20:55:01.413 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28997660 M=4767004 E=1555141 D=9336900 T=44656705 Oct 01 20:55:01.706 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28997660 M=4767004 E=1555141 D=9336900 T=44656705 Oct 01 21:55:01.518 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29035750 M=4774946 E=1555567 D=9329490 T=44695753 Oct 01 21:55:01.748 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29035750 M=4774946 E=1555567 D=9329490 T=44695753 Oct 01 22:55:01.585 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29056190 M=4903867 E=1568397 D=9394100 T=44922554 Oct 01 22:55:01.821 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29056190 M=4903867 E=1568397 D=9394100 T=44922554 Oct 01 23:55:01.601 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29094570 M=4866122 E=1564312 D=9414730 T=44939734 Oct 01 23:55:01.849 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29094570 M=4866122 E=1564312 D=9414730 T=44939734 Oct 02 00:55:01.699 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29106630 M=4966697 E=1552942 D=9422670 T=45048939 Oct 02 00:55:01.950 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29106630 M=4966697 E=1552942 D=9422670 T=45048939 Oct 02 01:55:01.587 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29095030 M=4958196 E=1544129 D=9398470 T=44995825 Oct 02 01:55:01.820 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29095030 M=4958196 E=1544129 D=9398470 T=44995825 Oct 02 02:55:01.519 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29073860 M=4921832 E=1518622 D=9409240 T=44923554 Oct 02 02:55:01.756 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29073860 M=4921832 E=1518622 D=9409240 T=44923554 Oct 02 03:55:01.656 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29054920 M=4895233 E=1522200 D=9472470 T=44944823 Oct 02 03:55:01.902 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29054920 M=4895233 E=1522200 D=9472470 T=44944823 Oct 02 04:55:01.935 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29044680 M=4862168 E=1491624 D=9427500 T=44825972 Oct 02 04:55:02.176 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29044680 M=4862168 E=1491624 D=9427500 T=44825972 Oct 02 05:55:01.552 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29015410 M=4830524 E=1485998 D=9434010 T=44765942 Oct 02 05:55:01.815 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29015410 M=4830524 E=1485998 D=9434010 T=44765942 Oct 02 06:55:01.558 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29012780 M=4815414 E=1477433 D=9419850 T=44725477 Oct 02 06:55:01.806 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29012780 M=4815414 E=1477433 D=9419850 T=44725477 Oct 02 07:55:01.623 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28970740 M=4734512 E=1493034 D=9413870 T=44612156 Oct 02 07:55:01.863 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28970740 M=4734512 E=1493034 D=9413870 T=44612156 Oct 02 08:55:01.570 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28967330 M=4726078 E=1473119 D=9417080 T=44583607 Oct 02 08:55:01.828 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28967330 M=4726078 E=1473119 D=9417080 T=44583607 Oct 02 09:55:01.750 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28974330 M=4742600 E=1514309 D=9416520 T=44647759 Oct 02 09:55:02.007 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28974330 M=4742600 E=1514309 D=9416520 T=44647759 Oct 02 10:55:01.608 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28979430 M=4770044 E=1526874 D=9410090 T=44686438 Oct 02 10:55:01.844 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=28979430 M=4770044 E=1526874 D=9410090 T=44686438 Oct 02 11:55:01.547 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29006090 M=4817310 E=1539612 D=9390510 T=44753522 Oct 02 11:55:01.794 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29006090 M=4817310 E=1539612 D=9390510 T=44753522 Oct 02 12:55:01.537 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29024340 M=4751606 E=1518839 D=9396840 T=44691625 Oct 02 12:55:01.798 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29024340 M=4751606 E=1518839 D=9396840 T=44691625 Oct 02 13:55:01.418 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29078440 M=4731478 E=1554244 D=9409910 T=44774072 Oct 02 13:55:01.691 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29078440 M=4731478 E=1554244 D=9409910 T=44774072 Oct 02 14:55:01.685 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29083630 M=4758160 E=1543378 D=9414920 T=44800088 Oct 02 14:55:01.928 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29083630 M=4758160 E=1543378 D=9414920 T=44800088 Oct 02 15:55:01.614 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29091410 M=4803451 E=1522298 D=9417970 T=44835129 Oct 02 15:55:01.849 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29091410 M=4803451 E=1522298 D=9417970 T=44835129 Oct 02 16:55:01.643 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29112080 M=4777827 E=1545239 D=9395200 T=44830346 Oct 02 16:55:01.882 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29112080 M=4777827 E=1545239 D=9395200 T=44830346 Oct 02 17:55:01.440 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29110070 M=4778454 E=1572919 D=9392920 T=44854363 Oct 02 17:55:01.697 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29110070 M=4778454 E=1572919 D=9392920 T=44854363 Oct 02 18:55:01.493 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29067918 M=4894213 E=1586776 D=9388330 T=44937237 Oct 02 18:55:01.732 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29067918 M=4894213 E=1586776 D=9388330 T=44937237 Oct 02 19:55:01.408 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29074618 M=4901792 E=1512712 D=9387300 T=44876422 Oct 02 19:55:01.642 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29074618 M=4901792 E=1512712 D=9387300 T=44876422 Oct 02 20:55:01.546 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159418 M=4953782 E=1520874 D=9376230 T=45010304 Oct 02 20:55:01.785 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29159418 M=4953782 E=1520874 D=9376230 T=45010304 Oct 02 21:55:01.482 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29164138 M=4975927 E=1542930 D=9392050 T=45075045 Oct 02 21:55:01.740 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29164138 M=4975927 E=1542930 D=9392050 T=45075045 Oct 02 22:55:01.589 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29174537 M=5076124 E=1536717 D=9353310 T=45140688 Oct 02 22:55:01.839 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29174537 M=5076124 E=1536717 D=9353310 T=45140688 Oct 02 23:55:01.600 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29245184 M=5079399 E=1553941 D=9376610 T=45255134 Oct 02 23:55:01.848 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29245184 M=5079399 E=1553941 D=9376610 T=45255134 Oct 03 00:55:01.609 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29298413 M=5150012 E=1579298 D=9370340 T=45398063 Oct 03 00:55:01.851 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29298413 M=5150012 E=1579298 D=9370340 T=45398063 Oct 03 01:55:01.599 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29274432 M=5140570 E=1570971 D=9362930 T=45348903 Oct 03 01:55:01.852 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29274432 M=5140570 E=1570971 D=9362930 T=45348903 Oct 03 02:55:01.515 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29255605 M=5056604 E=1563181 D=9374230 T=45249620 Oct 03 02:55:01.749 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29255605 M=5056604 E=1563181 D=9374230 T=45249620 Oct 03 03:55:01.595 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29220975 M=5027355 E=1526417 D=9353340 T=45128087 Oct 03 03:55:01.867 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29220975 M=5027355 E=1526417 D=9353340 T=45128087 Oct 03 04:55:01.574 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29285464 M=5010122 E=1555168 D=9293930 T=45144684 Oct 03 04:55:01.809 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29285464 M=5010122 E=1555168 D=9293930 T=45144684 Oct 03 05:55:01.569 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29293360 M=5014422 E=1561660 D=9305050 T=45174492 Oct 03 05:55:01.809 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29293360 M=5014422 E=1561660 D=9305050 T=45174492 Oct 03 06:55:01.492 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29224770 M=4963965 E=1550564 D=9271500 T=45010799 Oct 03 06:55:01.773 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29224770 M=4963965 E=1550564 D=9271500 T=45010799 Oct 03 07:55:01.598 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29229449 M=4876547 E=1532620 D=9277330 T=44915946 Oct 03 07:55:01.839 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29229449 M=4876547 E=1532620 D=9277330 T=44915946 Oct 03 08:55:01.560 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29217377 M=4844463 E=1537916 D=9241080 T=44840836 Oct 03 08:55:01.808 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29217377 M=4844463 E=1537916 D=9241080 T=44840836 Oct 03 09:55:01.673 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29213206 M=4765949 E=1548770 D=9261520 T=44789445 Oct 03 09:55:01.925 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29213206 M=4765949 E=1548770 D=9261520 T=44789445 Oct 03 10:55:01.703 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29186577 M=4754825 E=1548367 D=9278150 T=44767919 Oct 03 10:55:01.954 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29186577 M=4754825 E=1548367 D=9278150 T=44767919 Oct 03 11:55:01.650 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29229307 M=4744016 E=1534473 D=9302670 T=44810466 Oct 03 11:55:01.892 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29229307 M=4744016 E=1534473 D=9302670 T=44810466 Oct 03 12:55:01.631 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29233177 M=4716556 E=1501191 D=9309600 T=44760524 Oct 03 12:55:01.878 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29233177 M=4716556 E=1501191 D=9309600 T=44760524 Oct 03 13:55:01.519 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29211147 M=4764532 E=1474727 D=9286280 T=44736686 Oct 03 13:55:01.756 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29211147 M=4764532 E=1474727 D=9286280 T=44736686 Oct 03 14:55:01.611 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29148699 M=4640457 E=1495711 D=9334355 T=44619222 Oct 03 14:55:01.868 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29148699 M=4640457 E=1495711 D=9334355 T=44619222 Oct 03 15:55:01.614 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29175399 M=4676542 E=1529010 D=9335420 T=44716371 Oct 03 15:55:01.875 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29175399 M=4676542 E=1529010 D=9335420 T=44716371 Oct 03 16:55:01.536 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29187830 M=4689331 E=1523055 D=9303910 T=44704126 Oct 03 16:55:01.786 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29187830 M=4689331 E=1523055 D=9303910 T=44704126 Oct 03 17:55:01.541 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29187519 M=4717900 E=1598430 D=9284650 T=44788499 Oct 03 17:55:01.778 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29187519 M=4717900 E=1598430 D=9284650 T=44788499 Oct 03 18:55:01.389 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29173080 M=4900934 E=1608874 D=9289010 T=44971898 Oct 03 18:55:01.629 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29173080 M=4900934 E=1608874 D=9289010 T=44971898 Oct 03 19:55:01.618 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29194273 M=4935540 E=1491949 D=9307240 T=44929002 Oct 03 19:55:01.857 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29194273 M=4935540 E=1491949 D=9307240 T=44929002 Oct 03 20:55:01.433 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29208643 M=5110627 E=1522271 D=9294310 T=45135851 Oct 03 20:55:01.674 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29208643 M=5110627 E=1522271 D=9294310 T=45135851 Oct 03 21:55:01.423 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29249463 M=5116138 E=1504559 D=9294750 T=45164910 Oct 03 21:55:01.685 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29249463 M=5116138 E=1504559 D=9294750 T=45164910 Oct 03 22:55:01.455 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29266753 M=5130870 E=1511809 D=9313750 T=45223182 Oct 03 22:55:01.704 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29266753 M=5130870 E=1511809 D=9313750 T=45223182 Oct 03 23:55:01.661 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29307573 M=5030964 E=1493530 D=9321390 T=45153457 Oct 03 23:55:01.903 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29307573 M=5030964 E=1493530 D=9321390 T=45153457 Oct 04 00:55:01.624 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29330613 M=5141074 E=1487463 D=9346720 T=45305870 Oct 04 00:55:01.862 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29330613 M=5141074 E=1487463 D=9346720 T=45305870 Oct 04 01:55:01.821 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29316833 M=5106803 E=1507539 D=9344260 T=45275435 Oct 04 01:55:02.071 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29316833 M=5106803 E=1507539 D=9344260 T=45275435 Oct 04 02:55:01.702 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29439583 M=5071526 E=1540628 D=9363460 T=45415197 Oct 04 02:55:01.941 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29439583 M=5071526 E=1540628 D=9363460 T=45415197 Oct 04 03:55:01.639 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29442380 M=5082011 E=1584268 D=9366890 T=45475549 Oct 04 03:55:01.875 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29442380 M=5082011 E=1584268 D=9366890 T=45475549 Oct 04 04:55:01.661 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29320470 M=5028803 E=1603456 D=9372050 T=45324779 Oct 04 04:55:01.901 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29320470 M=5028803 E=1603456 D=9372050 T=45324779 Oct 04 05:55:01.432 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29450730 M=4834327 E=1545462 D=9425820 T=45256339 Oct 04 05:55:01.654 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29450730 M=4834327 E=1545462 D=9425820 T=45256339 Oct 04 06:55:01.498 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29501530 M=4810364 E=1556306 D=9446220 T=45314420 Oct 04 06:55:01.738 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29501530 M=4810364 E=1556306 D=9446220 T=45314420 Oct 04 07:55:01.443 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29526890 M=4701757 E=1532561 D=9442110 T=45203318 Oct 04 07:55:01.669 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29526890 M=4701757 E=1532561 D=9442110 T=45203318 Oct 04 08:55:01.524 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29551400 M=4618528 E=1588496 D=9407410 T=45165834 Oct 04 08:55:01.748 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29551400 M=4618528 E=1588496 D=9407410 T=45165834 Oct 04 09:55:01.505 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29574040 M=4659891 E=1579306 D=9409640 T=45222877 Oct 04 09:55:01.797 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29574040 M=4659891 E=1579306 D=9409640 T=45222877 Oct 04 10:55:01.463 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29565110 M=4605165 E=1581448 D=9423660 T=45175383 Oct 04 10:55:01.687 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29565110 M=4605165 E=1581448 D=9423660 T=45175383 Oct 04 11:55:01.505 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29502830 M=4610175 E=1588201 D=9425820 T=45127026 Oct 04 11:55:01.732 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29502830 M=4610175 E=1588201 D=9425820 T=45127026 Oct 04 12:55:01.458 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29517360 M=4600025 E=1580463 D=9421320 T=45119168 Oct 04 12:55:01.698 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29517360 M=4600025 E=1580463 D=9421320 T=45119168 Oct 04 13:55:01.441 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29466440 M=4620573 E=1443890 D=9373381 T=44904284 Oct 04 13:55:01.678 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29466440 M=4620573 E=1443890 D=9373381 T=44904284 Oct 04 14:55:01.437 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29495430 M=4635023 E=1417409 D=9344261 T=44892123 Oct 04 14:55:01.691 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29495430 M=4635023 E=1417409 D=9344261 T=44892123 Oct 04 15:55:01.431 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29500990 M=4576385 E=1413535 D=9352071 T=44842981 Oct 04 15:55:01.654 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29500990 M=4576385 E=1413535 D=9352071 T=44842981 Oct 04 16:55:01.555 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29539140 M=4448554 E=1381861 D=9363151 T=44732706 Oct 04 16:55:01.780 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29539140 M=4448554 E=1381861 D=9363151 T=44732706 Oct 04 17:55:01.748 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29037030 M=4856142 E=1567967 D=9214551 T=44675690 Oct 04 17:55:01.981 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29037030 M=4856142 E=1567967 D=9214551 T=44675690 Oct 04 18:55:01.567 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29322240 M=4721546 E=1522058 D=9273571 T=44839415 Oct 04 18:55:01.809 [notice] Computed bandwidth weights for Case 3a (E scarce) with v10: G=29322240 M=4721546 E=1522058 D=9273571 T=44839415
(Yes, I really am producing two of those lines for each consensus period. Maybe one for each consensus flavor? I haven't looked into it.)
Changed 3 years ago by
Attachment: | computed-bandwidth-weights-moria1-sep2014-oct2014 added |
---|
Changed 3 years ago by
Attachment: | computed-bandwidth-weights-moria1-jul2013-oct2013 added |
---|
comment:49 Changed 3 years ago by
And I just attached two more from the distant past, to give you a bit more variety.
comment:50 Changed 3 years ago by
Keywords: | nickm-deferred-20161005 added |
---|---|
Milestone: | Tor: 0.2.9.x-final → Tor: 0.3.0.x-final |
Deferring big/risky-feature things (even the ones I really love!) to 0.3.0. Please argue if I'm wrong.
comment:51 Changed 3 years ago by
These have sat in needs_revision for a few weeks at least. Removing from review-group-9, not adding to review-group-10.
comment:52 Changed 3 years ago by
Keywords: | review-group-10 added |
---|
Add 0.3.0 needs_review items (and ones that haven't been in needs_revision for very long) to review-group-10.
comment:53 Changed 3 years ago by
Updated branch (https://github.com/pastly/public-tor/tree/ticket14881-v2) with tests involving real data. Thanks arma.
comment:54 Changed 3 years ago by
Status: | needs_revision → needs_review |
---|
comment:55 Changed 3 years ago by
Keywords: | review-group-9 removed |
---|
comment:56 Changed 3 years ago by
Resolution: | → fixed |
---|---|
Status: | needs_review → closed |
This looks safe enough. I'm going to rebase and re-merge, though, since the original merge was faulty: It re-used consensus method 24, when it should have allocated a new consensus method. I've grabbed 26. Thanks for all the work!
Pastly, would you like to take a go at #20060 ?
comment:57 Changed 3 years ago by
Replying to teor:
Replying to pastly:
...
- 1/10000 does not sound like a lot to me. If this is a big enough concern, we'll have to figure something else out.
I'm not worried about the inaccuracy, but I'd like to know what the impact is - where does the extra weight change which nodes we choose, and how often? Which nodes get chosen more often because of it?
For the record, this is the impact of this patch in the public Tor network:
- each category gains a very small increment, which has negligible impact on the final weights,
And on very small or very new Tor networks:
- each category is weighted at least 1, even if there are no relays for that category. This may be good, because it allows the calculation to proceed. But it might also make some cases unreachable (if they rely on zero values), or add weight for things that aren't there.
We should run this consensus method on the tor test network before the 0.3.0 Tor release.
comment:58 follow-up: 60 Changed 3 years ago by
I've tested this in chutney now. One set of tests was run at the tip of current master, which includes this ticket, and is commit 48d7b69. The other set is a few commits back, does not include this ticket, and is commit 5a1779b.
I ran basic-min, bridges-ipv6-min, bridges-min, hs-ipv6, hs-min, ipv6-exit-min, mixed, single-onion, and single-onion-ipv6.
I wrote a script to see what nodes, if any, fail to bootstrap based on the presense of "Bootstrapped 100" in notice.log. The following output is the same with and without this ticket.
./nodes.basic-min/000a/ probably failed to bootstrap ./nodes.basic-min/001a/ probably failed to bootstrap ./nodes.basic-min/002r/ probably failed to bootstrap ./nodes.bridges-ipv6-min/000a/ probably failed to bootstrap ./nodes.bridges-ipv6-min/001ba/ probably failed to bootstrap ./nodes.bridges-ipv6-min/002r/ probably failed to bootstrap ./nodes.bridges-min/000a/ probably failed to bootstrap ./nodes.bridges-min/001ba/ probably failed to bootstrap ./nodes.bridges-min/002r/ probably failed to bootstrap ./nodes.ipv6-exit-min/000a/ probably failed to bootstrap ./nodes.ipv6-exit-min/001a/ probably failed to bootstrap ./nodes.ipv6-exit-min/002r/ probably failed to bootstrap
make test-network-all
says all PASS with and without this ticket.
With this ticket, the authorities output lines like the following.
Oct 26 18:53:35.000 [notice] Time to compute a consensus. Oct 26 18:53:35.000 [notice] Computed bandwidth weights for Case 2b1 (Wgg=weight_scale, Wmd=Wgd) with v10: G=1 M=1 E=1 D=1 T=4 Oct 26 18:53:35.000 [notice] Bandwidth-weight Case 1 is verified and valid. Oct 26 18:53:35.000 [notice] Computed bandwidth weights for Case 2b1 (Wgg=weight_scale, Wmd=Wgd) with v10: G=1 M=1 E=1 D=1 T=4 Oct 26 18:53:35.000 [notice] Bandwidth-weight Case 1 is verified and valid. Oct 26 18:53:35.000 [notice] Consensus computed; uploading signature(s) Oct 26 18:53:35.000 [notice] Signature(s) posted. Oct 26 18:53:35.000 [notice] Uploaded signature(s) to dirserver 127.0.0.1:7001 Oct 26 18:53:35.000 [notice] Got a signature from 127.0.0.1. Adding it to the pending consensus. Oct 26 18:53:35.000 [notice] Added a signature for test001a from 127.0.0.1. Oct 26 18:53:36.000 [notice] Time to fetch any signatures that we're missing. Oct 26 18:53:36.000 [notice] Time to publish the consensus and discard old votes Oct 26 18:53:36.000 [notice] Published ns consensus
And the bandwidth-weights
line in the consensus is always
bandwidth-weights Wbd=3333 Wbe=0 Wbg=0 Wbm=10000 Wdb=10000 Web=10000 Wed=3333 Wee=10000 Weg=3333 Wem=10000 Wgb=10000 Wgd=3333 Wgg=10000 Wgm=10000 Wmb=10000 Wmd=3333 Wme=0 Wmg=0 Wmm=10000
Without this ticket, the authorities output lines like the following.
Oct 26 19:55:59.000 [notice] Time to compute a consensus. Oct 26 19:55:59.000 [warn] Consensus with empty bandwidth: G=0 M=0 E=0 D=0 T=0 Oct 26 19:55:59.000 [warn] Consensus with empty bandwidth: G=0 M=0 E=0 D=0 T=0 Oct 26 19:55:59.000 [notice] Consensus computed; uploading signature(s) Oct 26 19:55:59.000 [notice] Signature(s) posted. Oct 26 19:55:59.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:55:59.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:55:59.000 [warn] Failed to find node for hop 1 of our path. Discarding this circuit. Oct 26 19:55:59.000 [notice] Uploaded signature(s) to dirserver 127.0.0.1:7001 Oct 26 19:55:59.000 [notice] Got a signature from 127.0.0.1. Adding it to the pending consensus. Oct 26 19:55:59.000 [notice] Added a signature for test001a from 127.0.0.1. Oct 26 19:56:00.000 [notice] Time to fetch any signatures that we're missing. Oct 26 19:56:00.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:56:00.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:56:00.000 [warn] Failed to find node for hop 1 of our path. Discarding this circuit. Oct 26 19:56:01.000 [notice] Time to publish the consensus and discard old votes Oct 26 19:56:01.000 [notice] Published ns consensus
And there is no bandwidth-weights line.
I hope this helps answer some questions.
Changed 3 years ago by
Attachment: | test_network_log_with14881.tar.xz added |
---|
Changed 3 years ago by
Attachment: | test_network_log_without14881.tar.xz added |
---|
comment:59 Changed 3 years ago by
Oh, one final comment to make something explicit. Consensus method 2b1 was always used in the with14881
networks. No method was used in the without14881
networks because networkstatus_compute_bw_weights_v10
refuses to do so if G, M, E, or D are <= 0.
comment:60 Changed 3 years ago by
Replying to pastly:
I've tested this in chutney now. One set of tests was run at the tip of current master, which includes this ticket, and is commit 48d7b69. The other set is a few commits back, does not include this ticket, and is commit 5a1779b.
I ran basic-min, bridges-ipv6-min, bridges-min, hs-ipv6, hs-min, ipv6-exit-min, mixed, single-onion, and single-onion-ipv6.
I wrote a script to see what nodes, if any, fail to bootstrap based on the presense of "Bootstrapped 100" in notice.log. The following output is the same with and without this ticket.
./nodes.basic-min/000a/ probably failed to bootstrap ./nodes.basic-min/001a/ probably failed to bootstrap ./nodes.basic-min/002r/ probably failed to bootstrap ./nodes.bridges-ipv6-min/000a/ probably failed to bootstrap ./nodes.bridges-ipv6-min/001ba/ probably failed to bootstrap ./nodes.bridges-ipv6-min/002r/ probably failed to bootstrap ./nodes.bridges-min/000a/ probably failed to bootstrap ./nodes.bridges-min/001ba/ probably failed to bootstrap ./nodes.bridges-min/002r/ probably failed to bootstrap ./nodes.ipv6-exit-min/000a/ probably failed to bootstrap ./nodes.ipv6-exit-min/001a/ probably failed to bootstrap ./nodes.ipv6-exit-min/002r/ probably failed to bootstrap
make test-network-all
says all PASS with and without this ticket.
I logged #20473 for this issue.
With this ticket, the authorities output lines like the following.
Oct 26 18:53:35.000 [notice] Time to compute a consensus. Oct 26 18:53:35.000 [notice] Computed bandwidth weights for Case 2b1 (Wgg=weight_scale, Wmd=Wgd) with v10: G=1 M=1 E=1 D=1 T=4 Oct 26 18:53:35.000 [notice] Bandwidth-weight Case 1 is verified and valid. Oct 26 18:53:35.000 [notice] Computed bandwidth weights for Case 2b1 (Wgg=weight_scale, Wmd=Wgd) with v10: G=1 M=1 E=1 D=1 T=4 Oct 26 18:53:35.000 [notice] Bandwidth-weight Case 1 is verified and valid. Oct 26 18:53:35.000 [notice] Consensus computed; uploading signature(s) Oct 26 18:53:35.000 [notice] Signature(s) posted. Oct 26 18:53:35.000 [notice] Uploaded signature(s) to dirserver 127.0.0.1:7001 Oct 26 18:53:35.000 [notice] Got a signature from 127.0.0.1. Adding it to the pending consensus. Oct 26 18:53:35.000 [notice] Added a signature for test001a from 127.0.0.1. Oct 26 18:53:36.000 [notice] Time to fetch any signatures that we're missing. Oct 26 18:53:36.000 [notice] Time to publish the consensus and discard old votes Oct 26 18:53:36.000 [notice] Published ns consensusAnd the
bandwidth-weights
line in the consensus is always
bandwidth-weights Wbd=3333 Wbe=0 Wbg=0 Wbm=10000 Wdb=10000 Web=10000 Wed=3333 Wee=10000 Weg=3333 Wem=10000 Wgb=10000 Wgd=3333 Wgg=10000 Wgm=10000 Wmb=10000 Wmd=3333 Wme=0 Wmg=0 Wmm=10000
Without this ticket, the authorities output lines like the following.
Oct 26 19:55:59.000 [notice] Time to compute a consensus. Oct 26 19:55:59.000 [warn] Consensus with empty bandwidth: G=0 M=0 E=0 D=0 T=0 Oct 26 19:55:59.000 [warn] Consensus with empty bandwidth: G=0 M=0 E=0 D=0 T=0 Oct 26 19:55:59.000 [notice] Consensus computed; uploading signature(s) Oct 26 19:55:59.000 [notice] Signature(s) posted. Oct 26 19:55:59.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:55:59.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:55:59.000 [warn] Failed to find node for hop 1 of our path. Discarding this circuit. Oct 26 19:55:59.000 [notice] Uploaded signature(s) to dirserver 127.0.0.1:7001 Oct 26 19:55:59.000 [notice] Got a signature from 127.0.0.1. Adding it to the pending consensus. Oct 26 19:55:59.000 [notice] Added a signature for test001a from 127.0.0.1. Oct 26 19:56:00.000 [notice] Time to fetch any signatures that we're missing. Oct 26 19:56:00.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:56:00.000 [warn] No available nodes when trying to choose node. Failing. Oct 26 19:56:00.000 [warn] Failed to find node for hop 1 of our path. Discarding this circuit.
I logged #20474 for this error.
Oct 26 19:56:01.000 [notice] Time to publish the consensus and discard old votes
Oct 26 19:56:01.000 [notice] Published ns consensus
}}}
And there is no bandwidth-weights line.
I hope this helps answer some questions.
Thanks for this, it looks like the patch should make chutney and small networks more reliable.
comment:61 Changed 3 years ago by
For the record, the test network will run this consensus method once we all upgrade to tor 0.3.0.1-alpha (or an 0.3.0-alpha-dev containing this particular commit).
comment:62 Changed 3 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
On clang 3.9.0, i386, macOS Sierra, this patch causes the following warnings:
src/test/test_dir.c:2049:18: error: implicit conversion loses integer precision: 'long long' to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~^~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:158:22: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:26: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:116:16: note: expanded from macro 'tt_assert_test_fmt_type' type val1_ = (a); \ ~~~~~ ^ src/test/test_dir.c:2049:29: error: implicit conversion loses integer precision: 'int64_t' (aka 'long long') to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~~~~~~~~~~~~^~ ./src/ext/tinytest_macros.h:158:24: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:28: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:117:16: note: expanded from macro 'tt_assert_test_fmt_type' type val2_ = (b); \ ~~~~~ ^ src/test/test_dir.c:2064:18: error: implicit conversion loses integer precision: 'long long' to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~^~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:158:22: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:26: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:116:16: note: expanded from macro 'tt_assert_test_fmt_type' type val1_ = (a); \ ~~~~~ ^ src/test/test_dir.c:2064:29: error: implicit conversion loses integer precision: 'int64_t' (aka 'long long') to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~~~~~~~~~~~~^~ ./src/ext/tinytest_macros.h:158:24: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:28: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:117:16: note: expanded from macro 'tt_assert_test_fmt_type' type val2_ = (b); \ ~~~~~ ^ src/test/test_dir.c:2079:18: error: implicit conversion loses integer precision: 'long long' to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~^~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:158:22: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:26: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:116:16: note: expanded from macro 'tt_assert_test_fmt_type' type val1_ = (a); \ ~~~~~ ^ src/test/test_dir.c:2079:29: error: implicit conversion loses integer precision: 'int64_t' (aka 'long long') to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~~~~~~~~~~~~^~ ./src/ext/tinytest_macros.h:158:24: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:28: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:117:16: note: expanded from macro 'tt_assert_test_fmt_type' type val2_ = (b); \ ~~~~~ ^ src/test/test_dir.c:2094:18: error: implicit conversion loses integer precision: 'long long' to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~^~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:158:22: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:26: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:116:16: note: expanded from macro 'tt_assert_test_fmt_type' type val1_ = (a); \ ~~~~~ ^ src/test/test_dir.c:2094:29: error: implicit conversion loses integer precision: 'int64_t' (aka 'long long') to 'long' [-Werror,-Wshorten-64-to-32] tt_int_op(G+M+E+D, OP_EQ, T); ~~~~~~~~~~~~~~~~~~~~~~~~~~^~ ./src/ext/tinytest_macros.h:158:24: note: expanded from macro 'tt_int_op' tt_assert_test_type(a,b,#a" "#op" "#b,long,(val1_ op val2_), \ ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:144:28: note: expanded from macro 'tt_assert_test_type' tt_assert_test_fmt_type(a,b,str_test,type,test,type,fmt, \ ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ./src/ext/tinytest_macros.h:117:16: note: expanded from macro 'tt_assert_test_fmt_type' type val2_ = (b);
It looks like the unit tests need to consistently use int64_t, rather than assuming that long is always 64 bits.
comment:63 Changed 3 years ago by
tt_i64_op() is the right way to handle int64 comparisons like this.
comment:64 follow-up: 66 Changed 3 years ago by
Status: | reopened → needs_review |
---|
Yet another branch with the change recommended by nickm.
https://github.com/pastly/public-tor/tree/ticket14881-v4
I don't have a 32bit machine of any kind to test.
comment:65 Changed 3 years ago by
Looks safe; merged that. I'll close once we see whether 32-bit is fixed now.
comment:66 Changed 3 years ago by
Resolution: | → fixed |
---|---|
Status: | needs_review → closed |
Yes, this compiles without warnings on macOS 10.12 clang i386.
Replying to pastly:
I don't have a 32bit machine of any kind to test.
Fair enough.
(macOS on x86_64 compiles and emulates i386 code, so that's what I use.)
Not many of us have big-endian machines, either.
Except apparently for debian's build farm, which catches bugs like this.
comment:67 Changed 3 years ago by
Here's what 25 and 26 look like on the test network, 12 hours apart:
bandwidth-weights Wbd=0 Wbe=0 Wbg=4081 Wbm=10000 Wdb=10000 Web=10000 Wed=10000 Wee=10000 Weg=10000 Wem=10000 Wgb=10000 Wgd=0 Wgg=5919 Wgm=5919 Wmb=10000 Wmd=0 Wme=0 Wmg=4081 Wmm=10000
bandwidth-weights Wbd=0 Wbe=0 Wbg=3974 Wbm=10000 Wdb=10000 Web=10000 Wed=10000 Wee=10000 Weg=10000 Wem=10000 Wgb=10000 Wgd=0 Wgg=6026 Wgm=6026 Wmb=10000 Wmd=0 Wme=0 Wmg=3974 Wmm=10000
They're almost identical - it seems the change is lost in the actual bandwidth changes on the network, and the calculations, which is what we wanted to see.
There's also no issue with the test network swapping between 25 and 26, we've done that a few times now, as the authority with the casting vote on the consensus method was on a laptop.
patch to change only in testing networks