Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] - Slow download speeds compared to direct downloads #85

Closed
JasonLandbridge opened this issue Oct 3, 2021 · 5 comments
Closed
Labels
bug Something isn't working fixed Issues that are assumed fixed before being closed

Comments

@JasonLandbridge
Copy link
Collaborator

JasonLandbridge commented Oct 3, 2021

It has been reported several times that certain servers have a much slower download speed when using PlexRipper, compared to direct downloading through a browser. I have been able to reproduce this so I will investigate this, I hope to have a fix in the next release as this is a high priority one.

image

Workaround:

Downloading something will show a "graph icon" next to it on the download page. Click it and it will open some details which include a direct download link:

image

@JasonLandbridge JasonLandbridge added the bug Something isn't working label Oct 3, 2021
@imTHAI
Copy link

imTHAI commented Jan 29, 2022

I have this problem, I came here to report it and found your ticket.

@EricLauber
Copy link

@JasonLandbridge I have found that the link you are indicating here hasn't worked for me. I had to make a change and add a query parameter.

Instead of
http://SERVER:PORT/KEY?X-Plex-Token=TOKEN, I had to use http://SERVER:PORT/KEY?download=1&X-Plex-Token=TOKEN.

@BakasuraRCE
Copy link

Hey @JasonLandbridge this is a buffer problem, check this:
https://stackoverflow.com/questions/39353119/filestream-readasync-very-slow-compared-to-read

I Just the 4096 by 524288000(500 MB) and disabled the throttledStream, done! full speed

byte[] buffer = new byte[4096];

@JasonLandbridge
Copy link
Collaborator Author

@BakasuraRCE thank you so much! This was indeed the issue and I have been able to fix this in the latest v0.9.0 release. I've given you an honorable mention in the release notes

@JasonLandbridge JasonLandbridge added the fixed Issues that are assumed fixed before being closed label Nov 29, 2022
@BakasuraRCE
Copy link

With pleasure, always willing to help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed Issues that are assumed fixed before being closed
Projects
None yet
Development

No branches or pull requests

4 participants