The single player/single stream tests are largely complete
- Test 27 (Direct to Origin)
- Test 28 (Direct to midtier, coldcache)
- Test 29 (Direct to midtier, warmcache)
- Test 30 (Cold edge, warm midtier)
- Test 31 (Warm edge, Warm midtier)
- Test 32 (Cold edge, cold midtier)
- Test 33 (Artificially warmed Edge 1)
The result of Test 33 in particular was quite surprising. The edge showed good cache efficiency (4/5 requests were cache_hits) but the player still didn't attempt to play bitrates above 1024.
Test 34 will repeat Test 33 to see if the same behaviour is observed
- Test 34 (Artificially warmed Edge 1 - repeat of Test 33)
- Test 35 - Two players, cold edge
- Test 36 - Two players, warm edge
- Test 37 - Two players, warm edge
- Test 38 - Two players, warm edge
Unsurprisingly, the main finding is that as the cache warms, the players average choice of bitrate increases.
Was in the process of setting up a multi client test, but the midtier is currently unavailable.
tor.log shows
Dec 26 21:10:10.000 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
Can't see any other issues in the log, which suggests it may be the guard. Have moved all cached data out of the way and restarted Tor to try and get a new guard, but no dice.
Will have to leave it for 10 minutes and see if the issue resolves
Kinda underlines the need for multiple caches at the midtier in a production environment. Also important that caches use different guards so that an issue in one doesn't take too large a proportion of the infrastructure out.
Activity
2015-12-18 16:54:57
2015-12-24 13:12:07
2015-12-24 14:02:39
2015-12-24 14:08:15
- Test 27 (Direct to Origin)
- Test 28 (Direct to midtier, coldcache)
- Test 29 (Direct to midtier, warmcache)
- Test 30 (Cold edge, warm midtier)
- Test 31 (Warm edge, Warm midtier)
- Test 32 (Cold edge, cold midtier)
- Test 33 (Artificially warmed Edge 1)
The result of Test 33 in particular was quite surprising. The edge showed good cache efficiency (4/5 requests were cache_hits) but the player still didn't attempt to play bitrates above 1024.
Test 34 will repeat Test 33 to see if the same behaviour is observed
2015-12-26 15:29:33
2015-12-26 15:31:04
- Test 34 (Artificially warmed Edge 1 - repeat of Test 33)
- Test 35 - Two players, cold edge
- Test 36 - Two players, warm edge
- Test 37 - Two players, warm edge
- Test 38 - Two players, warm edge
Unsurprisingly, the main finding is that as the cache warms, the players average choice of bitrate increases.
2015-12-26 21:22:01
tor.log shows
Can't see any other issues in the log, which suggests it may be the guard. Have moved all cached data out of the way and restarted Tor to try and get a new guard, but no dice.
Will have to leave it for 10 minutes and see if the issue resolves
2015-12-26 21:53:04
Kinda underlines the need for multiple caches at the midtier in a production environment. Also important that caches use different guards so that an issue in one doesn't take too large a proportion of the infrastructure out.
2016-01-10 21:16:01
2016-01-10 21:16:01
2016-01-10 21:16:40
2016-01-10 21:16:46
2016-01-10 21:34:14
2016-01-10 21:34:14
2016-01-10 21:34:41
2016-01-10 21:34:45