Bandwidth throttling about client HOT 12 CLOSED

OK is this a dead end?

No one assigned and no expected delivery. Very frustrating, perhaps no one else suffers from this?

Just kills the project for us :-(

from client.

This is in the roadmap, but need to get a few things set first.

from client.

Definitely borders on show-stopper for me, which is unfortunate. It's such a darned great application in general!

from client.

This affects me as well. Using trickle (https://wiki.archlinux.org/index.php/Trickle) doesn't help.

from client.

This really does need to be fixed. It's a show stopper. My shared host has flood control on a massive number of php calls from the same ip address. So sync from client for more than a few hundred files becomes impossible.
Back to rsync for the moment.

from client.

@bbguitar A show stopper is a bug that affects everyone, this is not the case. It might be a show stopper for you, but in your case, this is due to the amount of money that you are willing to invest in your webspace. Also, throttling bandwidth will not help if those files are small ones, you will still have the same number of php calls. Uploading a file that is 10kb of size will take the same time with a 10Mbit connection as with a 0,5Mbit connection.
My personal opinion on that: you should either talk to your shared hoster or invest a bit more in your webspace.

from client.

I agree that 'bandwidth limiting' won't fix the PHP issue bbguitar is having (though a 'files-per-minute' option would handle that, I feel like there's a VERY small number of folks who would want that feature).

Regarding a lack of bandwidth-throttling being a "show-stopper" - I think the specifics of the terminology isn't the point; it's pretty crazy that it's not a feature; Some examples of tools that have it? Dropbox, Rsync, scp, wget, filezilla-client. As far as I can tell, SeaFile doesn't, nor does SparkleShare. (The former has it planned ffor .17, the latter says they cant' do so due to the git backend).

Anyway - considering large parts of the world have bandwidth caps on internet connectivity, and many folks care about keeping their networks healthy, bandwidth limiting is a dang important feature.

from client.

ne_set_notifier(fn, user_data) gives you a callback executed at various events, including an "I just sent out 8KB of data!" event. Setting such a notifier callback that checks the upload rate for the past 30 seconds and calls nanosleep(2) when it gets too high should work for throttling. (Then there's the UI for selecting how heavily to throttle and bookkeeping for how much data has been sent over how long a period.)

from client.

@ogoffart @guruz you might find this bandwidth throttling idea above interesting

from client.

It looks like you guys are using csync and not neon, though, so that's pretty useless.

from client.

@dhasenan Well, our csync module uses neon :-)

from client.

Jup, @dhasenan see http://code.woboq.org/owncloud/csync/modules/csync_owncloud.c.html :)

from client.