1 |
Am Wed, 15 Mar 2017 21:24:10 +0800 |
2 |
schrieb Danny YUE <sheepduke@×××××.com>: |
3 |
|
4 |
> Hi guys, |
5 |
> |
6 |
> I just got Steam installed and running successfully on my machine, |
7 |
> and tried to get CS:GO running smoothly, which made me really |
8 |
> happy :-D |
9 |
> |
10 |
> However when Steam is downloading games, the speed is extremely slow, |
11 |
> down to several KB/s, even some bytes/s. |
12 |
> I have already installed dnsmasq and it *was* good during downloading |
13 |
> CS:GO (~4MB/s), but became slow again with Civilization V. |
14 |
> |
15 |
> I googled a lot but all point to installing dnsmasq, which I don't |
16 |
> think is really helpful since I already have done that... |
17 |
> |
18 |
> Also I'm sure downloading region is correct. |
19 |
> |
20 |
> Anybody experienced the same issue with dnsmasq installed? |
21 |
> Any clue is welcome and thanks in advance. |
22 |
|
23 |
Here, it's downloading with peak bandwidths of 48 mbytes/s but usually |
24 |
it's around 38 mbytes/s. However, I sometimes see slowdowns, too. I |
25 |
guess that games are downloaded file by file, and when a lot of small |
26 |
files are left in the queue, it just cannot get good bandwidth. |
27 |
|
28 |
But I only see such slowdowns mostly short before the last few |
29 |
megabytes of a game. |
30 |
|
31 |
Could you check if your downloaded games consist of many smallish |
32 |
files? Then that could be the explanation. |
33 |
|
34 |
You could try activating fq_codel and tcp fastopen: |
35 |
|
36 |
In /proc/sys/net/ipv4/tcp_fastopen it should say 1. |
37 |
In /proc/sys/net/core/default_qdisc it should say fq_codel. |
38 |
|
39 |
Also, you may want to try out bbr congestion control: |
40 |
|
41 |
In /proc/sys/net/ipv4/tcp_congestion_control it should say bbr. |
42 |
|
43 |
By recompiling the kernel, you can reconfigure the defaults for this |
44 |
(and enable support). Some of these need modern kernels. |
45 |
|
46 |
Additionally, many small tcp request need a good portion of your upload |
47 |
bandwidth and are very dependent on good round trip times. Traditional |
48 |
DSL lines with ping times of 50-60ms can really slow down requests of |
49 |
small files a lot due to three-way tcp handshaking, that is, you could |
50 |
request only one smallish file per 100-120ms. This can totally destroy |
51 |
the usable bandwidth. Maybe watch a running ping while the downloads |
52 |
are running. If the ping times increase while the download slows down, |
53 |
your bottleneck is the upload. |
54 |
|
55 |
But also keep in mind that traditional spinning disks may not keep up |
56 |
with the bandwidth if confronted with many small files. If you're using |
57 |
SSD all should be fine. I'm running on bcache with writeback caching |
58 |
which gives a really good performance boost by adding a small SSD to |
59 |
one or more big HDDs. |
60 |
|
61 |
-- |
62 |
Regards, |
63 |
Kai |
64 |
|
65 |
Replies to list-only preferred. |