Opened 8 years ago

Closed 2 years ago

#4506 closed task (wontfix)

Simulate the N23 design to see how it performs for typical and for really slow client connections

Reported by: karsten Owned by: arma
Priority: Medium Milestone:
Component: Metrics/Analysis Version:
Severity: Keywords: performance flowcontrol
Cc: iang, malsabah@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This project ticket has the sole purpose of combining the N23 simulation tickets that are due March 15, 2012. The actual work should take place in the child tickets.

Child Tickets

TicketStatusOwnerSummaryComponent
#4487closedResearch: Does N23 help especially much in cases where the first hop is slow/flaky?Metrics/Analysis
#4488closedTrack down the N23 patch, then update it for modern TorCore Tor/Tor
#5333closedMake simulator authors aware of "clients have different connectivity" wishlist itemMetrics/Analysis
#5379newDesign adaptive n23 algorithm that worksCore Tor/Tor
#5392needs_revisionWrite proposal for n23 patch behaviorCore Tor/Tor
#7346newAdd stream-level pushback into n23 designCore Tor/Tor

Change History (12)

comment:1 Changed 8 years ago by karsten

Keywords: performance flowcontrol added

comment:2 Changed 8 years ago by karsten

Cc: arma added
Owner: karsten deleted
Status: newassigned

This is sponsor F deliverable 9.

Unassigning this ticket from me. Roger, is this a project you could lead? If so, can you assign it to yourself? If not, who would be a good person leading it?

comment:3 Changed 8 years ago by karsten

Cc: arma removed
Owner: set to arma

Roger said he's already kinda leading this deliverable, so he's fine if I assign this ticket to him.

comment:4 Changed 8 years ago by karsten

Milestone: Sponsor F: March 15, 2012
Type: projecttask

Removing the Sponsor F: March 15, 2012 milestone. Task 9 of that milestone was to evaluate feasibility of simulating N23, not to run the simulations, which is blocking on simulator improvements independent of N23.

comment:5 Changed 7 years ago by karsten

Keywords: SponsorF20121101 added
Type: taskproject

Roger and I discussed sponsor F deliverables at the Florence hackfest. Making this ticket the ticket for sponsor F deliverable 9 again. What we did in #4488, which is a child ticket of this ticket, technically completed that deliverable, but we should aim for more.

comment:6 Changed 7 years ago by iang

Cc: iang added

comment:7 Changed 7 years ago by karsten

Simulation of the n23-4 branch failed as further described in #4486. Is there anything else we can/should do here before the November 1 deadline?

comment:8 Changed 7 years ago by karsten

November 1 has passed, and it seems highly unlikely that we'll complete this ticket including all its child tickets in the next few days. Shall we make #4488 the project ticket for sponsor F year 2 item 9 again and change this ticket to a normal task ticket?

If nobody comes up with a better plan, I'll do that in a few days.

comment:9 in reply to:  8 Changed 7 years ago by arma

Replying to karsten:

November 1 has passed, and it seems highly unlikely that we'll complete this ticket including all its child tickets in the next few days. Shall we make #4488 the project ticket for sponsor F year 2 item 9 again and change this ticket to a normal task ticket?

If nobody comes up with a better plan, I'll do that in a few days.

Yes, that sounds good. I've updated the wiki page.

comment:10 Changed 7 years ago by karsten

Keywords: SponsorF20121101 removed
Type: projecttask

Making #4488, not #4506, the project ticket for sponsor F year 2 item 9.

comment:11 Changed 7 years ago by Mashael

Cc: malsabah@… added

comment:12 Changed 2 years ago by karsten

Resolution: wontfix
Status: assignedclosed

Closing tickets in Metrics/Analysis that have been created 5+ years ago and not seen progress recently, except for the ones that "nickm-cares" about.

Note: See TracTickets for help on using tickets.