Opened 12 years ago

Last modified 17 months ago

#2042 new bug

WebUI incredibly slow with 1500 torrents

Reported by: eatnumber1 Owned by: damoxc
Priority: blocker Milestone: performance
Component: Web UI Version: 1.3-stable
Keywords: lockup crash freeze lock Cc: eatnumber1, bro, marsjaninzmarsa@…


This is exactly the same problem as #1026, but as that one was fixed, I'm opening a new ticket.

deluged: 1.3.3

Google Chrome: 17.0.963.56

I have about 1500 torrents added. Similarly to #1026, if I show less torrents by choosing a different label, the ui gets much faster.

I can send a tarball of my config directory, just need to know where to send it.

Change History (11)

comment:1 Changed 12 years ago by Cas

  • Summary changed from WebUI locks up/gets incredibly slow when there are many torrents to WebUI incredibly slow with 1500 torrents

comment:2 Changed 12 years ago by Cas

How many columns have you enabled?

comment:3 Changed 12 years ago by eatnumber1

I had all 14 of them enabled. I just disabled a few and the UI got more responsive, but it's still quite slow.

comment:4 Changed 11 years ago by Cas

  • Milestone changed from Future to performance

comment:5 Changed 11 years ago by mauromi

  • Priority changed from major to blocker
  • Version changed from 1.3.3 to 1.3.6

i have the same problem with 500 ...

comment:6 Changed 10 years ago by Simbiat

Same is true with latest 1.4 build. As I suggested on the forum: GUI tries to update every torrent one by one, which causes excessive access to state file. It's an assumption, but a possibility. Or at least it may be somewhere in there. because if you parse the file directly in text format or something - it gets about 15 seconds to get all the info... Also, if you check the state file there are a lot of lines like "aI1". Like too many, making the file ~3 times larger than it should be.

comment:7 Changed 10 years ago by bro

It has nothing to do with excessive access to state file, it's all in memory when being updated. The code that updates the ui simply has to be optimized. Also, some new changes to the core (hopefully) will make is possible to just update the entries that have changed for each update.

comment:8 Changed 8 years ago by bro

  • Cc bro added

Add bro to cc

comment:9 Changed 7 years ago by marsjaninzmarsa

  • Cc marsjaninzmarsa@… added

comment:10 Changed 5 years ago by int3l

  • Version changed from 1.3.6 to 1.3-stable

comment:11 Changed 17 months ago by Xuefer

"The connection to the webserver has been lost!" on heavy load (too many torrents, etc)

Note: See TracTickets for help on using tickets.