Opened 13 years ago

Closed 12 years ago

#1455 closed feature-request (Invalid)

deluge/libtorrent should utilize multiple processors when checkin files

Reported by: balaton Owned by:
Priority: trivial Milestone:
Component: libtorrent Version: other (please specify)
Keywords: Cc:


Currently, deluge/libtorrent seems to use only one processor for checking torrents. Using multiple proccessors on a multicore/multicpu machine could speed up this process rapidly.

Change History (7)

comment:1 Changed 13 years ago by andar

  • Status changed from new to pending

I suspect the bottleneck happens more from disk I/O than cpu. Have you gathered any statistics to prove otherwise? What data have you gathered that you're willing to share?

comment:2 Changed 13 years ago by balaton

  • Status changed from pending to new

I ran a deluged on a dedicated machine and had it run a check of a torrent. I measured the disk i/o with iotop and it way about 30mb/s read and basically no writes. From that I concluded that there would be plenty of room to check another torrent simultaniously.

comment:3 Changed 13 years ago by Glieb

Right now a moderately fast dual core processor can handle checking of a dozen torrents even with one core. Implementing this for the few systems that have a slow dual core processor and a fast disk is pointless. Besides, I think it is bad for HDD durability if the head has to move back and forth between two torrents for checking. Especially if the CPU is actually capable to max out the disk I/O bottleneck.

comment:4 Changed 13 years ago by Cas

  • Milestone changed from 1.3.x to Future

comment:5 Changed 13 years ago by Cas

  • Milestone Future deleted

comment:6 Changed 13 years ago by Cas

  • Priority changed from major to trivial

comment:7 Changed 12 years ago by Cas

  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.