Page 1 of 1

0.7.4 slow to respond to api add file

Posted: October 16th, 2012, 5:28 am
by clinton hall
Recently there have been issues in CouchPotato where the same movie is downloaded numerous times. The cause appears to be the comma between SABnzbd and CouchPotatoServer. When CPS sends the nzb via api, sab starts downloading, but CPS shows a timeout error waiting for a response (timeout = 60 s).

Today I ran some "speed" tests with adding nzb via api. Usually about 2 seconds, but occasionally up to 9 seconds.
Then when my wife added a whole 720p season of a TV show from SickBeard, the next TV snatch actually sent the nzb twice and still the show is not showing as snatched.

I then re did the speed tests and the first attempt to add timed out at 500 s!
This is with a queue in SABnzbd of about 15 GiB.

So it appears that SAB is slow to respond to api calls when it is busy/under load.

We are trying to look at recent changes to CPS as this updates 4 days ago, but Sab also updated 14 days ago... Somewhere the combination appears to cause issues when trying to add new downloads while downloading, and it appears can also cause issues with SickBeard.

Our discussions and tests to date are here https://github.com/RuudBurger/CouchPota ... issues/924

Re: 0.7.4 slow to respond to api add file

Posted: October 16th, 2012, 5:49 am
by clinton hall
Ok, tests with an older version of CPS have indicated that 0.7.4 works fine ;)

As far as my system bogging down with a large download queue.. Well... It is a small arm processor ;)

Re: 0.7.4 slow to respond to api add file

Posted: October 16th, 2012, 11:53 am
by shypike
SABnzbd is a bit slow in processing large NZB files, also because a lot of disk files need to be created.
Combined with heavy downloading, it can be even slower.
You'll see the same thing happen if you upload such an NZB manually.