ติดตั้ง Steam
เข้าสู่ระบบ
|
ภาษา
简体中文 (จีนตัวย่อ)
繁體中文 (จีนตัวเต็ม)
日本語 (ญี่ปุ่น)
한국어 (เกาหลี)
български (บัลแกเรีย)
Čeština (เช็ก)
Dansk (เดนมาร์ก)
Deutsch (เยอรมัน)
English (อังกฤษ)
Español - España (สเปน)
Español - Latinoamérica (สเปน - ลาตินอเมริกา)
Ελληνικά (กรีก)
Français (ฝรั่งเศส)
Italiano (อิตาลี)
Bahasa Indonesia (อินโดนีเซีย)
Magyar (ฮังการี)
Nederlands (ดัตช์)
Norsk (นอร์เวย์)
Polski (โปแลนด์)
Português (โปรตุเกส - โปรตุเกส)
Português - Brasil (โปรตุเกส - บราซิล)
Română (โรมาเนีย)
Русский (รัสเซีย)
Suomi (ฟินแลนด์)
Svenska (สวีเดน)
Türkçe (ตุรกี)
Tiếng Việt (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
กระทู้นี้ได้ถูกล็อกแล้ว 
ผู้สร้างกระทู้นี้ได้ทำเครื่องหมายโพสต์เป็นคำตอบสำหรับคำถามของตน
กฎและแนวทางปฏิบัติในกระดานสนทนา
รายงานโพสต์นี้
http://steamcommunity.com/discussions/forum/10/350541595116544893/
The only ones responding here are users and mods who are just basically users with slightly more powers to do stuff.
So you might as well give up asking for certain responses (Things I don't want/Things I do want), you are not going to get them.
If it uses too much bandwidth, then turn down the amount of bandwidth it uses. I used to let Steam use all the bandwidth it wanted, but I had issues with other computers and other software trying to connect. Now I only let steam use 2/3 of the bandwidth I want, but every other computer on the network doesn't have any issues connecting to the net.
I do the same but it always seems odd to me I have to manually set this up - I can download a dozen large files simultaneously in two or three different browsers and generally can carry on doing stuff as normal, no matter that they are running my connection flat out between them (or maybe just close to it). But if I download one game on Steam without having it choked back everything that relies on my connection starts suffering - even Steam itself grinds to a near halt (to the point where if you buy one game and start installing it, browsing to and buying the next game before the first finishes is painful, and frequently errors).
It is still fairly odd to me that such a fundamental part of what Steam is for is still so bad at its job that you have to manually control it to avoid it trashing the experience of using steam, and that it has been this way for so many years now.
Clearly they've reaslised it's an issue because they automatically pause downloads when you're in a game, however they haven't taken the obvious next step , which is to realise that other people on the same network might be playing a game while you're downloading something.
If your router or network card cannot handle multiple HTTP requests at the same time
1) Update your network card drivers
2) hard reset your router
There is no reason why HTTP downloads should 'kill' anything because steam does not make 'more' requests than you hitting YouTube
You are trying to solve the wrong problem. Your issue has nothing to do with threads, its because your internet is slow. Feel free to limit the amount of bandwidth steam uses so it doesnt saturate your network.
What normally happens is Steam will get to the point where it hits diminishing returns on new connections, and stop opening more. I'm running a little download experiment right now, and I'm topping out at 12.5 MB/s with 6 connections.
Steam in general asks the backend for 20 possible download sources, which means, for some reason, as you say it's opening 20 connections, that it's hitting the maximum possible number of connections. What's odd is that it implies your connection has some fairly atypical characteristics; it's weird that it takes up to 20 connections to get to the saturation point, and it's weird that the performance drop-off on your connection is so sharp that at 19 connections Steam is still getting a perf improvement from additional connections but the 20th totally hoses your connection. That seems odd to me.
If you run a download then post up your Steam/logs/content_log.txt it might shed some light on what's going on; that log does include some info on the decision Steam makes to open new connections.
Steam's been automatically pausing downloads when you're in a game since before it even used HTTP to do downloads; these are not connected things.
So you can see it went up to 6 connections and topped out there.
20 HTTP downloads and 20 STEAM connections are *NOT* the same thing at all. Steam's CDN intentionally oversaturates your connection, if you pull it up in wireshark you might see up to 7% TCP retransmissions, versus regular connections, which adjust to the available bandwith and back-off properly. It might look like a "reguar HTTP connection", but there's also some witchcraft behind the scenes.
Part of the issue is opening 20 connections when 3 connections would have been sufficient to saturate the bandwith. The algorithm is broken and will open 10-20 connections in very many cases. But that's not the only issue. The issue is they've done something in the backend that defeats proper congestion control, such that 20 HTTP connections in your web browser poses very little problem, while 20 Steam connections causes excess packet loss or latency.
I've troubleshooted this at length with 4 different routers. This is not an issue with my equipment.
The only time I've seen a connection not struggle with steam is a fiber connection.
If you're not willing to benchmark the effect on your latency of 20 HTTP downloads, vs 20 steam connections, you really have no say in this matter, you're just blaming the user.
While I don't have access to dozens of internet connections to confirm my findings, I've tested quite a few, enough to see a trend and a problem.
But Steam downloads just kill my internet. I really want to be able to tell it: ONE connection only. More than that likely makes no sense to open more conns with my measly 8Mbits anyway.
With anything below 10 connections I can still play online while downloading with maximum speed with pings staying well below 100ms when staying within my continent (5-10ms when idle). Good enough for space sims and strategy games.
But when Steam downloads stuff, I can barely browse the internet anymore. The only thing that keeps working well is IRC. ;)
I want a way to configure this behavior!!
So check msconfig and disable that from startup, if you see it there.
It is explained here :
https://support.steampowered.com/kb_article.php?ref=9828-SFLZ-9289
Peer-to-Peer (P2P) Clients & File Sharing Software
P2P programs have the potential to consume a large portion of your bandwidth or other system resources if not properly configured. This can prevent connections or traffic that Steam depends on, while also interfering with resources required by games. It is not recommended to have file sharing applications active while you are using Steam.
It has something to do with AKAmai FastTCP. Beyond the scope of my understanding. Still would like to see a connection limiter builtin.
I don't mean that my Internet would be dying because of Steam and Bittorrent fighting for bandwidth. I'm not perma-leeching or seeding or anything. ;)
What I meant was: When downloading with Bittorrent (as long as I limit the conns to ~20) without Steam running, my Internet is still snappy and fast enough, like when browsing the web via HTTP.
When my Bittorrent client process is terminated, and I'm downloading via Steam (so only Steam consumes bandwidth), everything turns into a crawl and browsing the web becomes painful. I haven't inspected the traffic actually (like with Wireshark), so I'm not sure what it's doing, but whatever it is, it's not good.
I hope this explains the situation better.
I would like a small configuration option added to Steam so I can limit the connection count per download. This is assuming that the count is the reason for this. But it's quite reasonable to think so.
If I blow up my Bittorrent connection count to around 100 (meaning 100 active connections transferring data), the behavior is somewhat similar to what Steam is doing to my INet while downloading. This can easily be tested by downloading e.g. large Linux DVD ISOs with tons of seeders via some Bittorrent client, and configuring that client to allow for a high connection count per download. Wait for it to open up lots of connections and see what it does to your web browsing experience.
I'm not aware of any differences between qBitttorrent and µTorrent in that respect, but then again... I never really compared them like that either, so I couldn't say.
It'll be interesting to see what it shows because in my case my Steam connections cap out at either the initial 4, or immediately after adding a 5th connection.
I'm pretty sure I know what Steam is doing (it's trying to get the download speed to an acceptable rate regardless of congestion on the network) which because of the sheer congestion on your network (note this doesn't necessarily mean just your network, it can extend out to your ISP and how they route to the specific Steam download servers the bottleneck causing Steam to hammer the connection) is causing it to have to spawn a large number of connections, but the content of the logs should help confirm that (as well as indicate to you what would happen if it didn't have that many connections as far as your download speed goes).