Pogoplug V2, slow Crashplan transfers

[titojackson]

Hello all,

I have a v2 pogoplug running Crashplan under Arch. I have it set up with the headless configuration - SSH in and tunnel ports through to get the Crashplan client to read the pogo's crashplan engine data. Everything works!

EXCEPT: My uploads to the crashplan servers starts off at around 2Mbps and drops soon after and stays at around 200Kbps. Crashplan transfers from other computers running (windows XP) stay at around 2 Mbps for the duration of the transfer. Transfers from the pogo to other computers on the LAN consistently hit around 8 MB/sec.

It's not the hardware specs of the Pogo
It's not my upload bandwidth, also Crashplan support said they do not throttle traffic. My ISP also doesn't seem to be throttling traffic on my other computers.
All packages have been updated/upgraded on the pogo.
I have samba, openntpd, and crashplan running. Arch is installed on a 4GB flash drive.
Ports are forwarded to the pogo through my TPLINK router.

So my question is what could possibly be slowing down the transfer? I figured it must be a configuration issue with Arch. Thank you very much in advance.

tjackson

[WarheadsSE]

So:

xp->pogo->CP servers ?

Have you watched the load with htop as this was occurring?

[titojackson]

It's pogo >crashplan. The XP machine is just running the client app displaying config info from the crashplan service on the pogo.

ok, installed htop and ready to go. What should I be looking for? Crashplan does seem to start a lot of processes, around 60. But it seems like they're all sleeping except one that does some work actively then switches with another process.


Let me know what else I can provide.

[WarheadsSE]

My immediate guess: the compression and encryption is taking it's toll.

[titojackson]

I thought the same and turned them off. It seemed to make not make a big difference to cpu usage - and transfer speeds were still hovering around 200kbps.

[titojackson]

Also I just noticed that stopping and restarting the crashplan service gets me an unpredictable amount of time at full upload speeds before it settles back to 200 kbps- ish.

[WarheadsSE]

Do you has nss installed?

[titojackson]

nss 3.14-1 is in the list of packages installed. I've never messed with it.

[titojackson]

Hello all,

I've been screwing around with the pogoplug v2 for a while now and looking for answers to the slow transfer issue and I've decided to give up. Even with all encryption and compression and deduplication features turned off, and only 1x2 gig file is being sent transfers will be slow due to Crashplan.

When crashplan is allowed to take up 100% of cpu time, htop shows low ram usage, and 100% cpu usage. However when crashplan is only allowed 50% maximum cpu time, htop shows around 50-60% usage and the transfer speed goes from (now) 230 kbps to about 130 kbps - pretty linear drop.

For anyone googling their way here, Pogoplug V2 and Crashplan is a good idea, but slow due to Crashplan's processing requirements.

[WarheadsSE]

Make sure you have an up-to-date bootloader, then look into the linux-kirkwood kernel, as it has the BFQ scheduler, which will help with heavier loads.