Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#895 closed Enhancement (fixed)

don't scrape running torrents on startup

Reported by: charles Owned by: charles
Priority: Normal Milestone: 1.20
Component: libtransmission Version: 1.11
Severity: Normal Keywords:
Cc:

Description

Currently we send out a scrape shortly after adding a torrent, whether it's going to be running or not. This is bad because:

(1) We don't get any new information out of it. The scrape response is a subset of the announce response, and if they're sent in a short period of time the response is likely to be the same.

(2) The cost of getting that duplicate information comes in the form of extra network load to the tracker.

Change History (4)

comment:1 Changed 14 years ago by charles

  • Status changed from new to assigned
  • Summary changed from on startup, no need to scrape started torrents to don't scrape running torrents on startup

comment:2 Changed 14 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:3 Changed 14 years ago by charles

r5697: fixes r5695 error that didn't turn scraping back on after at torrent had been stopped.

comment:4 Changed 14 years ago by charles

  • Type changed from Bug to Enhancement
Note: See TracTickets for help on using tickets.