Opened 7 weeks ago

Last modified 10 days ago

#29291 new defect

Work out a better way to choose the data size to download

Reported by: juga Owned by:
Priority: Medium Milestone: sbws: unspecified
Component: Core Tor/sbws Version: sbws: 1.0.2
Severity: Normal Keywords: changes-version-patch, sbws-11x-final-removed-20190312
Cc: karsten, irl Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

Instead of starting to download 16MB and adjust the size depending on how long it takes to download until a maximum of 1GB, we could:

  • Choose the initial size based on the bandwidth that the relay report
  • (Try to download for a maximum of 10secs? and) stop downloading data when we have learnt enough

Child Tickets

Change History (7)

comment:2 Changed 7 weeks ago by juga

Points: 0.4

comment:3 Changed 6 weeks ago by juga

Milestone: sbws: 1.0.x-finalsbws: 1.1.x-final
Points: 0.41

Minimum points is 1. We moved this to 1.1 milestone (or even later).

comment:4 Changed 6 weeks ago by juga

Cc: karsten irl added; juga removed

karsten and irl (CCed) plan to implement in onionperf the method they explained to me, which basically is:
Start downloading a big file and check (maybe every second?) when the download speed stabilizes, ie, doesn't change too much with respect to previous values. The speed at this point is the speed to be reported.

comment:5 Changed 10 days ago by juga

Keywords: changes-version-patch added

Add keyword to tickets that imply a change of version patch, since it might affect the results, but in a backwards compatible way and doesn't add functionality.

comment:6 Changed 10 days ago by juga

Keywords: sbws-11x-final-removed-20190312 added

Move tickets that can wait to next month

comment:7 Changed 10 days ago by juga

Milestone: sbws: 1.1.x-finalsbws: unspecified

Actually remove them from milestone

Note: See TracTickets for help on using tickets.