|
|
'''Scalability Project, Creating Funding Proposals'''
|
|
|
**Scalability Project, Creating Funding Proposals**
|
|
|
|
|
|
'''Goal: '''Understand next steps in scalability work, outline how we can approach funders with this project.
|
|
|
**Goal: **Understand next steps in scalability work, outline how we can approach funders with this project.
|
|
|
|
|
|
'''Where are we now?'''
|
|
|
**Where are we now?**
|
|
|
|
|
|
* Tor network capacity has increased over time
|
|
|
* But we need to make that experience more predictable, more uniform
|
... | ... | @@ -16,7 +16,7 @@ |
|
|
|
|
|
|
|
|
|
|
|
'''What is the benefit of a scalability project?'''
|
|
|
**What is the benefit of a scalability project?**
|
|
|
|
|
|
* Remove a major barrier for people to start and continue using Tor
|
|
|
* Give up because it’s slow: we want to retain users
|
... | ... | @@ -28,7 +28,7 @@ |
|
|
|
|
|
|
|
|
|
|
|
'''Who benefits from this?'''
|
|
|
**Who benefits from this?**
|
|
|
|
|
|
* Third party integrators
|
|
|
* Users under censorship
|
... | ... | @@ -36,7 +36,7 @@ |
|
|
|
|
|
|
|
|
|
|
|
'''Thinking through a phase 0-2 project'''
|
|
|
**Thinking through a phase 0-2 project**
|
|
|
|
|
|
1. Phase 0 is low hanging fruit
|
|
|
1. Phase 1 baseline metrics & measurements + building list of performance improvements & evaluating
|
... | ... | @@ -54,13 +54,13 @@ |
|
|
* Low-hanging single client tasks: we’re going to do two key performance changes; we’re going to test and see which one made the biggest difference
|
|
|
* We do tests, get results, not sure if we believe them, need experts to look over the data to verifying / figuring out what went wrong, debugging analysis (this is an important part of this proposal)
|
|
|
* Developing a new data model that will allow us to more quickly run experiments b/c we can design queries that help us look at the data quickly
|
|
|
* '''Staff: '''1 to 2 devs on network, 1 to 2 metrics/network health side
|
|
|
* '''Time: '''~6 months. Requires wall clock time to measure changes: at least weeks per experiment. Gets faster if we have both the machines & engineers to simultaneously compare Shadow to the live network—getting to the point that we can trust Shadow
|
|
|
* **Staff: **1 to 2 devs on network, 1 to 2 metrics/network health side
|
|
|
* **Time: **~6 months. Requires wall clock time to measure changes: at least weeks per experiment. Gets faster if we have both the machines & engineers to simultaneously compare Shadow to the live network—getting to the point that we can trust Shadow
|
|
|
* The more funding we get for this, the faster we can do these experiments, the better we get at this process, the faster we can provide results
|
|
|
|
|
|
|
|
|
|
|
|
'''After Phase 2, what happens?'''
|
|
|
**After Phase 2, what happens?**
|
|
|
|
|
|
* Start to add the dedicated network health monitoring, actively monitor the scan results and analyzing them
|
|
|
* Doing the queries over the metrics data —> contacting the relays & improving the network in this way
|
... | ... | @@ -70,6 +70,7 @@ |
|
|
* Research horizon
|
|
|
* Adding research programmers (would require a dedicated new developers)
|
|
|
|
|
|
'''What could third parties do to help this project?[[BR]]'''
|
|
|
'''What could third parties do to help this project?
|
|
|
'''
|
|
|
* Brave could help us understand what their users performance looks like on Tor. They may have their own user studies that can help tell us more about who/why/etc uses the Tor function.
|
|
|
* Bitcoin people? As China works towards censoring bitcoin, etc… |
|
|
\ No newline at end of file |