#2049 closed Bug (invalid)
"Torrent Properties" slow
| Reported by: | simonbcn | Owned by: | charles |
|---|---|---|---|
| Priority: | Normal | Milestone: | None Set |
| Component: | Qt Client | Version: | 1.60 |
| Severity: | Normal | Keywords: | |
| Cc: |
Description
When I double-click in a torrent, it opens the torrent properties window, but the information is updated after a few seconds, too much time in my opinion.
Change History (5)
comment:1 Changed 14 years ago by charles
- Resolution set to invalid
- Status changed from new to closed
comment:2 Changed 14 years ago by simonbcn
I don't agree. The webui is more responsive and more fast. The connections are the same for both.
comment:3 Changed 14 years ago by livings124
simonbcn: Feel free to hunt down the bug then.
comment:4 Changed 14 years ago by charles
The difference is that the Web UI is stupid -- it always asks the backend for everything, all the time. That's the main reason why the Web UI scales so poorly and is unusable when you have over 100 torrents.
The Qt interface only asks for the bare minimum needed to display the main window. If you open the properties dialog, then it starts asking the server for information needed by that dialog.
comment:5 Changed 14 years ago by simonbcn
ok, I understand.
Note: See
TracTickets for help on using
tickets.
This isn't its own bug.
What's happening is that the Qt client greys out the data until it gets a fresh update from the server, and the server is beign slow to respond.
The delay on the server side is very likely to be http://trac.transmissionbt.com/ticket/1753 but of course it's impossible to know from just looking at the Qt client end of things :)
If you'd like to monitor the daemon (one crude but simple way to do this is to run it in gdb, then hit ctrl-c and get a backtrace sometime in that four-second pause.