Here's a table of performance-related work where whole-network simulation can help:
| What? | Category | Expected Impact | Next step | When? |
|---|---|---|---|---|
| #4086 (moved): TokenBucketRefillInterval values | rate limiting | high | Figure out why graphs disagree | March2012 |
| #4682 (moved): "double door" effects on rate limiting | rate limiting | high | Simulate it in #5336 (moved) | March2012 |
| #4506 (moved): N23 | flow control | high | Simulate it in #4486 (moved) | March2012 |
| #4585 (moved): Read/write to fast relays more than slow ones | scheduling (conn) | high | Need to design/write a patch | |
| #5190 (moved): Throttle flows at guards | scheduling (conn) | high | Get patch from Rob | |
| #4684 (moved): Alternate transport between relays | various | high | Waiting for Steven to pick one | |
| #1854 (moved): Raise min bw for Fast flag | load balancing | medium | Simulators need to model relays better? | |
| #4485 (moved): Remove stream-level sendmes | flow control | low | Hoping we'll like n23 so it's moot | Nov2012 |
Below are a pile of tickets that are performance-related.
Flow control: TicketQuery(keywords=performance flowcontrol)
Load balancing: TicketQuery(keywords=performance loadbalancing)
Scheduling (streams, circuits, connections): TicketQuery(keywords=performance scheduling)
Client time-to-bootstrap: TicketQuery(keywords=performance bootstrap)
Making performance simulations more accurate: TicketQuery(keywords=performance simulation)
Scaling the network to make better use of the capacity we have: TicketQuery(keywords=performance scaling)
Improving the round-trip latency, or number of round-trips, for clients: TicketQuery(keywords=performance roundtrip)
Improving performance when using bridges: TicketQuery(keywords=performance bridges)
General / uncategorized: TicketQuery(keywords=performance)