Page 2 of 2

Re: Odroid C2 and DietPi -- Horribly Slow!

Posted: May 9th, 2018, 4:21 pm
by spazzed
Maybe I'm just expecting too much for an Odroid C2 to run radarr/sonarr/nzbhydra/plex server and SabNZBD?

Although, if I kill everything and only run SAB, it still peaks at 2.9MB/s.

Re: Odroid C2 and DietPi -- Horribly Slow!

Posted: May 10th, 2018, 12:54 am
by sander
Maybe. Maybe not.

But there are some bad signals:
swap being used 90%: sign of an overloaded system
htop shows "load average" with 4.89 and 9.24. Signs of an overloaded, unresponsive system (which you indeed experience)

After you killed all those other processes, were those numbers OK? Was SAB and your system reachable?

Oh, and:
- no wifi in place, I hope?
- article cache limit (/sabnzbd/config/general/#cache_limit) max 200M, I hope?
- number of SAB connections to newsservers: total not higher than 10, I hope?

EDIT:

sudo fdisk -l

... does that say anything about a ramdisk (I think recognizable as /dev/ram... )?

also: output of

mount

Re: Odroid C2 and DietPi -- Horribly Slow!

Posted: May 10th, 2018, 2:11 pm
by spazzed
I gave up and formatted and initialized a new system. Whatever was fubar'd on that one was driving me insane and the new one is downloading (and doing everything else I need it to do) waaaay faster. SAB is currently running w/ direct unpack and ssl at 16MB/s

I'll take it.

Re: Odroid C2 and DietPi -- Horribly Slow!

Posted: May 10th, 2018, 3:03 pm
by sander
Good decision. Nice speed! Question: is that the overall download speed of a big download (500 MB, 1000 MB)?

And what did you install? A fresh install of DietPi, or another OS?

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 10th, 2018, 3:41 pm
by spazzed
Odroid C2 w/ DietPi and running all of my services via docker-compose. It's working quite nicely so far.

I think my previous problem may have been related to a Jessie->stretch update. Everything claimed to be working but man it was dog slow and I don't know if there was a kernel issue or something else but it was butt.

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 11th, 2018, 10:02 am
by spazzed
Ack. I may have spoken too soon. System chugged along at 16MB/s for a few hours and then dropped down to 3-3.5.

Image

CPU utilization is low
Swap has capacity
RAM is available

The only other thing I can think but haven't tried is moving my incomplete/processing directory to my external drive. It seems like my SDCard should not be the bottleneck, though.

Any other ideas before I blow this docker up and switch to NZBGet to see if that's faster?

edit: If I reboot it does run fast for a while.

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 11th, 2018, 11:47 am
by safihre
Try setting the speed limit to 12MB/s

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 11th, 2018, 1:22 pm
by spazzed
safihre wrote: May 11th, 2018, 11:47 am Try setting the speed limit to 12MB/s
No effect. :/

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 11th, 2018, 4:21 pm
by spazzed
I eliminated the swap file altogether but it begs the question of why SAB is using so much mem? I have the cache set to 200M.

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 12th, 2018, 3:24 am
by safihre
Depends how big your queue is?

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 14th, 2018, 9:56 am
by spazzed
safihre wrote: May 12th, 2018, 3:24 am Depends how big your queue is?
My queue is large (although most of it is paused.) Is this the reason?

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 14th, 2018, 11:25 am
by safihre
Yes, queue-items take a bit of memory but with large queues (200+) this starts to add up.

Re: [RESOLVED] Odroid C2 and DietPi -- Horribly Slow!

Posted: May 14th, 2018, 2:57 pm
by spazzed
Found the magic bullet. Changed my temporary folder from the SD card to the external HDD and everything is working magically now. Great speeds and although I can't download at full speed while unpacking and verifying -- it does only slow down to ~5MB/s and it doesn't cripple my entire system. I also found out that the missing 300mb of RAM was being allocated to the GPU. Since I'm running this headless, I figured out how to edit boot.ini to reclaim that missing resource. Every bit helps!