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