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

Slow Blizzard speed? #2

Open
danny91 opened this issue Feb 5, 2017 · 6 comments
Open

Slow Blizzard speed? #2

danny91 opened this issue Feb 5, 2017 · 6 comments

Comments

@danny91
Copy link

danny91 commented Feb 5, 2017

Hi sorry to bother you, i'm struggling a bit hopefully someone can help me? The Steam part works fine and maxes out my 80mbit connection. However blizzard's only hits 2.5MB/s (Steam gets ~7). I was wondering if you may know what could be causing this? Thanks.

Talking about the initial download... After that it maxes out the gigabit network on a re-download.

My blizzard error log seems to have lots of errors... Any idea on this? http://pastebin.com/hb6WYC1Q

@ilumos
Copy link

ilumos commented Feb 5, 2017

Hi, thanks for reporting.

Try adding proxy_hide_header Etag; in upstreams/blizzard.conf in the location {} directive, clear the cache using scripts/clear-cache.sh and see if that results in better speed / no error log entries.

Many thanks

@danny91
Copy link
Author

danny91 commented Feb 6, 2017

Hi, thanks for your reply. That seems to have fixed the error's in the logs. However the speed does not seem to have increased. Still hovering around 2-3 MB/s. Any ideas? Thanks.

@ilumos
Copy link

ilumos commented Feb 6, 2017

I expect it is related to using slice but I do not know the best way to go about tuning this.

Perhaps try increasing or decreasing slice 1m and re-test?

Also, what hardware are you running this on re: CPU and storage?

Thanks

@danny91
Copy link
Author

danny91 commented Feb 6, 2017

Hi ill try see if changing it works. I5 @4gHz 32GB ram and 30TB zfs array. Nginx seems to only be using 3-6% Cpu so doesnt seem to be bottlenecking CPU wise. Might be to do with storage however it doesnt seem to be being hit too hard.

@ilumos
Copy link

ilumos commented Mar 5, 2017

ti-mo/ansible-lanparty have recently reverted to non-slice for Blizzard, citing an "nginx bug".

More detail than that I don't have. I've commented and hopefully they'll reply.

@ilumos
Copy link

ilumos commented Mar 6, 2017

Hi there,

ti-mo replied to the above linked issue and proxy_hide_header Etag; should have done the trick as mentioned previously.

Are you still having issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants