Are you being throttled?

[EricTheMagician]

Is anyone getting throttled by bitcasa? I used to be able to hit 20-30MB/s, but now I'm only getting 2-3.

I'm not really sure if it's my server, but I tested on my laptop and it seems like I am being throttled.

[saqebakhter]

Looks like it -

Monitoring eth0... (press CTRL-C to stop)

rx: 5.79 Mbit/s 520 p/s tx: 116 kbit/s 210 p/s

Used to get 45-50 Mbit/s -- that sucks...makes this whole effort useless :(

Maybe its an issue on there end ? Have you asked them?

[EricTheMagician]

I feel like they are actually throttling us.

On amazon EC2, it costs them at most 120$ / TB transferred out, and they may be trying to limit their bleeding.

Maybe you could ask their customer support?

I think they may know me and give me bs answers. Eric

On Thu, Sep 18, 2014 at 8:46 AM, saqebakhter notifications@github.com wrote:

Looks like it - Monitoring eth0... (press CTRL-C to stop) rx: 5.79 Mbit/s 520 p/s tx: 116 kbit/s 210 p/s Used to get 45-50 Mbit/s -- that sucks...makes this whole effort useless :(

Maybe its an issue on there end ?

Reply to this email directly or view it on GitHub: https://github.com/thejinx0r/BitcasaF4JS/issues/28#issuecomment-56032864

[saqebakhter]

I've submitted a request to ask them what the issue is.

Is it possible to pretend to be the desktop client, and use those APIs instead?

[saqebakhter]

Let me know if anything changes for you in terms of speeds. Better / Or / Worse.

[saqebakhter]

They replied saying they don't throttle...

[ghost]

Sure they replied that. How should they do that? Everyone use his own API Key, API Secret and so on...

[saqebakhter]

Any updates on this - anyone getting imporved speeds or its still not working? Makes this client slower than the offical one :(

Update speeds seem to be back to normal for me:

sakhter@sakhter-ubuntu:/mnt/BitcasaJS/Bitcasa Infinite Drive/Media/Movies2/Evil Dead (2013)$ rsync --partial --progress --append --rsh=ssh -r -h Evil\ Dead.mkv /tmp sending incremental file list Evil Dead.mkv 671.12M 14% 7.75MB/s 0:08:26

[EricTheMagician]

I've been away for a few days. Is it still back to normal?

[saqebakhter]

Yes looks normal to me..

[saqebakhter]

Speeds seem to be back to normal -but when transcoding with Plex - it does not transcode the whole file - sometimes just a few minutes of the episode (it thinks the file is done ) ...this is with the dev branch - not sure if you guys are running into this issue.....

[EricTheMagician]

That’s actually normal. Plex Server throttles the transcoding after it’s successfully transcoded a certain a mount of time so that it can stream to multiple users better.

You can change the time in the plex/web server settings. 

In the "advanced options" of the transcoder section, you can set the "Transcoder default throttle buffer”. I have mine set to 5 minutes (300 seconds).

Eric

On Tue, Sep 23, 2014 at 1:11 PM, saqebakhter notifications@github.com wrote:

Speeds seem to be back to normal -but when transcoding with Plex - it does not transcode the whole file - sometimes just a few minutes of the episode (it thinks the file is done ) ...this is with the dev branch - not sure if you guys are running into this issue.....

Reply to this email directly or view it on GitHub: https://github.com/thejinx0r/BitcasaF4JS/issues/28#issuecomment-56555007

[saqebakhter]

Nope - that's not what I meant - I use plexsync , when plex starts to transcode something with the dev branch it thinks it's done before the episode is actually done i.e) plex only transcodes, and syncs 5 minutes for a 40 minute show....

Using the offical client it works fine - it also used to work fine in the main branch, any idea what could be causing this or if you into this problem...?

[EricTheMagician]

I have some ideas on that might be causing it, but I'm not totally sure. Is it the same file that worked for you on the master branch and the dev branch? Or is it two different files?

[saqebakhter]

Same files.

Happens on multiple files / TV shows On Sep 25, 2014 4:02 AM, "thejinx0r" notifications@github.com wrote:

I have some ideas on that might be causing it, but I'm not totally sure. Is it the same file that worked for you on the master branch and the dev branch? Or is it two different files?

— Reply to this email directly or view it on GitHub https://github.com/thejinx0r/BitcasaF4JS/issues/28#issuecomment-56803429 .

[saqebakhter]

Still getting the same issues after the fixes you commited on the dev branch.

[saqebakhter]

I've gone back to the main branch as the incomplete transcodes are a show stopper for me.

[EricTheMagician]

I haven't had as much time recently to poke around with the code.

One of the problems I was having, was corrupted uploads when I was uploading large amounts of data through the developer api a while back. So files wouldn't download completely despite Bitcasa claiming that the whole file was there.

So, I started throwing errors instead of endlessly trying to redownload the file. Maybe that's the digression?

Anyways, I usually don't use the plex sync, but I will see if that is broken when I use it, and if it is, hopefully, it will be fixed.

[saqebakhter]

That would be great, thanks let me know - i can go back to dev branch and send you some logs if that would help as well.

[EricTheMagician]

I haven’t done anything yet, but I will reference this issue when I commit some fixes.

Eric

On Wed, Oct 1, 2014 at 12:58 PM, saqebakhter notifications@github.com wrote:

That would be great, thanks let me know - i can go back to dev branch and send you some logs if that would help as well.

Reply to this email directly or view it on GitHub: https://github.com/thejinx0r/BitcasaF4JS/issues/28#issuecomment-57498972