Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#4961 closed Bug (fixed)

Torrent with lot of files is slow

Reported by: hsn Owned by: jordan
Priority: Normal Milestone: 2.61
Component: Qt Client Version: 2.60
Severity: Normal Keywords:


If you have torrent containing lot of files (30k), then QT gui is way too slow to be used.

I want to choose which files to download. Click on torrent, then choose properties and everything does slow. Its not even needed to click on Files tab. If you click on Files, its almost impossible to scroll up/down and checkbox which files you want to download.

Change History (6)

comment:1 Changed 11 years ago by hsn

Its not QT core GUI issue because if you adding new torrent it works fine.

You choose File->Open select torrent, after few seconds dialog with listed files will be shown, now you can choose which ones you want to download at no performance problems there.

Performance problems are only if you want to modify already added torrent. I could not attach example torrent because there is way too low file attach limit but you can try this one: these ussualy have about 10k files.

comment:2 Changed 11 years ago by jordan

  • Milestone changed from None Set to 2.61
  • Status changed from new to assigned

comment:3 Changed 11 years ago by jordan

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

r13383 qt/ ( file-tree.h): (trunk, qt) #4961 -- make the file list more responsive when a torrent has an extreme number of files. Before this patch, the test torrent I had with ~10k files took 8 seconds to load. After this patch, it takes less than 1 second.

comment:4 Changed 11 years ago by rb07

Testing a torrent with a very large number of files (more than 65,000) gives this message on the console:

QObject::connect: Cannot queue arguments of type 'int64_t'
(Make sure 'int64_t' is registered using qRegisterMetaType().)

Is it related?

I don't see any 'connect' in the change, but the message doesn't appear with small torrents.

comment:5 Changed 11 years ago by jordan

rb07, I don't see that issue ... can you get a backtrace to see where it's coming from, then either reopen this ticket (if the error is in my new code) or open a new ticket for it...

comment:6 Changed 11 years ago by rb07


After building a debug version and running the same test twice the message did not appear (a breakpoint on the source of that message was never hit).

Note: See TracTickets for help on using tickets.