Opened 8 years ago

Closed 3 years ago

#7168 closed project (wontfix)

Get Torperf results to be more realistic

Reported by: karsten Owned by:
Priority: Medium Milestone:
Component: Archived/Torperf Version:
Severity: Normal Keywords:
Cc: ln5, ioerror, robgjansen, aagbsn, cass Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We should try to get Torperf results to be more realistic. Web pages are rather 320KB on average and contain multiple components, so our Torperf results are artificial.

We might need to do the redesign of Python parts (#2565) before extending Torperf towards a more complex download model. Setting up Torperf is already complex enough, and it's getting worse with every hack.

Child Tickets

#2565closedRedesign Python parts in TorperfArchived/Torperf
#7516closedTrack down Will Scott's torperf-like scripts, make them public if needed, and do a trial deployment somewhereArchived/Torperf
#7517closedDevise and deploy the canonical median web pageArchived/Torperf

Change History (3)

comment:1 Changed 4 years ago by cass

Cc: cass added
Severity: Normal

This ticket is tagged SponsorZ, but it looks like progress on it and its child tickets stalled two years ago. Is this still an active issue that needs funding?

comment:2 Changed 4 years ago by karsten

Keywords: SponsorZ removed

We're about to phase out Torperf and switch over to OnionPerf, so there's no need to find funding for this anymore. Removing the SponsorZ keyword. Thanks for asking.

comment:3 Changed 3 years ago by karsten

Resolution: wontfix
Status: newclosed

We officially switched from Torperf to OnionPerf for Tor performance measurements. We don't need these tickets anymore and will use OnionPerf's issue tracker for OnionPerf-related issues. Closing them all as wontfix.

Note: See TracTickets for help on using tickets.