Opened 16 years ago

Closed 15 years ago

#314 closed bug (WontFix)

Web seeding gets at 16kB rather than torrent piece size

Reported by: anonymous Owned by: markybob
Priority: major Milestone:
Component: 0.5.x Version: 0.5.9.2
Keywords: Cc:

Description

My access_log is showing that the Deluge 0.5.8.9 client is retrieving pieces at 16 kB instead of the piece size the torrent is designated for. In this case, the torrent piece size is 4MB. Other web server log entry is showing Deluge 0.5.8.4 is correctly retrieving the torrent piece size.

Attachments (1)

deluge0589.txt​ (23.8 KB) - added by anonymous 16 years ago.

Download all attachments as: .zip

Change History (6)

Changed 16 years ago by anonymous

comment:1 Changed 16 years ago by markybob

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

comment:2 Changed 16 years ago by markybob

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:3 Changed 16 years ago by markybob

  • Resolution set to invalid
  • Status changed from reopened to closed

comment:4 Changed 16 years ago by anonymous

  • Resolution invalid deleted
  • Status changed from closed to reopened

So, this "fixed" or is this "invalid"? I've had to ban all Deluge user agents from my web server because the client behaves like DDOS. The GetRight? implementation of webseed anyway retrieves rarest pieces in big chunks when possible. Deluge does not do this and consistently retrieves pieces at 16k when it could be retrieving them in 1MB, 2MB, or 4MB file pieces.

comment:5 Changed 15 years ago by markybob

  • Resolution set to wontfix
  • Status changed from reopened to closed

All 0.5 tickets are being closed. The branch is dead and won't be maintained any further.

Note: See TracTickets for help on using tickets.