Opened 11 months ago

Last modified 7 months 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: 1.2.x-final
Component: Core Tor/sbws Version: sbws: 1.0.2
Severity: Normal Keywords: sbws-11x-final-removed-20190312, scanner
Cc: karsten, irl Actual Points:
Parent ID: #29954 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 (11)

comment:2 Changed 11 months ago by juga

Points: 0.4

comment:3 Changed 10 months 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 10 months 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 9 months 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 9 months ago by juga

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

Move tickets that can wait to next month

comment:7 Changed 9 months ago by juga

Milestone: sbws: 1.1.x-finalsbws: unspecified

Actually remove them from milestone

comment:8 Changed 9 months ago by juga

Keywords: scanner added
Parent ID: #29954

comment:9 Changed 8 months ago by juga

I tried https://gist.github.com/juga0/4e29abef25c393e747e0a528749c11ba some months ago, but could not come out with a good way to check when the connection has been "stabilized".

comment:10 Changed 8 months ago by teor

Keywords: changes-version-patch removed

This ticket involves a major change to the sbws measurement method.
It should be added as a new, optional feature.
And then we should test it before making it the default.

We can't make major changes to the measurement method in a patch release. That's completely against semantic versioning. Patch releases contain small bugfixes, with predictable, low-risk outcomes.

comment:11 Changed 7 months ago by teor

Milestone: sbws: unspecifiedsbws: 1.2.x-final

It would be nice to make these changes in sbws 1.2

Note: See TracTickets for help on using tickets.