I am running sonarr on a Intel Atom 330 with 2GB RAM / Debian 8 - when adding (even after re-adding) the series “The Daily Show” the Series detail page does not show any episodes and keeps loading and loading.
The CPU usage does initially spike, but after that the usage is low and Disk/RAM is fine as well.
I suspect it is due to that show having a lot of episodes. Is there any reason why the application is trying to load all episodes on one page? Maybe it would be advisable to have different pages per season (e.g. /series/the-daily-show/season-1) ??
Sonarr pulls all the episode data back from the server, all 343 KB of it displays only the latest season from that (if its aired in the last 30 days), when you open a season it displays the episodes for that season, which varies, but tops around 160 in the last 4 seasons. The request itself takes a little while to load (8 seconds on my core2duo e8400), but it looks like we’re loading more information that we should, so we’ll get a fix out to correct that (in my tests its almost 4 times faster).
Typically loading screens that don’t disappear are caused by errors though, either on the server (check the log files) or purely on the client side, which would show in the debug console of the browser if they weren’t shown in the UI.
I don’t see us moving to an individual page per season or changing how the episodes are loaded.
Ok so the issue was that I was running it behind a reverse-proxy which had an upstream timeout of 60 seconds.
The question is now: why does the app need more than 60 seconds (!!!) to display a textual list of episodes by a series id?
e.g. the “offending” URL: /api/episode?seriesId=X
It seems like the database might not be made for this type of queries? Would it be feasible to switch over to something faster/better such as MySQL or MongoDB ?