安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
9 
举报此帖
And technocaly any nation at war will have network issue.
where the issue is, i do not know, but that will be my best guess, ( any network technician could tell you this. ) ask own ISP, dont count us to know traffic issue in your country.
keep in mind i try reply as neutral as i can, ask own ISP, best advice i can give you.
Steam can send 500mbps over the Atlantic ocean
Steam can push 1.5Tbps peak globally
Your download speeds are limited by
1) your cpu
2) your disk io
3) your anti-virus
4) your ISP
pick one
You are absolutely right about bottlenecks (CPU/Disk IO). That is precisely why this fix works.
The standard Steam interface for desktops consumes significantly more resources (Chromium instances) compared to the Big Picture overlay on some systems. Switching to BP frees up CPU/disk resources, allowing the decompression process to run faster. This is a software optimization issue, not an ISP issue. Thank you! :)
You are overlooking the relationship between the load on the user interface rendering and the decompression cycles associated with the CPU.
The standard Steam client relies heavily on Chromium Embedded Framework (CEF) instances (steamwebhelper), which can compete for thread priority and cause high CPU load during real-time decompression.
Switching to Big Picture mode changes the rendering pipeline (transferring UI calls to the GPU) and changes the process priority class. This reduces context switching and frees up CPU instruction cycles specifically for the decompression algorithm (LZMA/Zstd).
So yes, it does have a direct impact on effective throughput by removing the CPU bottleneck caused by the desktop UI. Thank you! :)
I appreciate your attempt to remain neutral and your concern. Greetings from Ukraine! 👋
However, from a technical standpoint, your hypothesis regarding ISP overcrowding or infrastructure degradation fails to explain the behavior I observed.
In network diagnostics, we have to isolate variables. If the bottleneck were truly caused by WAN latency, packet loss, or ISP throttling due to the geopolitical situation, changing the local graphical interface of the Steam client (switching to Big Picture) would have absolutely zero effect on the download throughput. The internet cable does not care which UI I am looking at.
The fact that the download speed saturates the bandwidth immediately after switching modes proves that the bottleneck is occurring at the local application layer (likely CPU thread scheduling or I/O overhead in the standard Desktop UI), not at the physical network layer.
So, while external factors exist, this specific solution addresses a software inefficiency, not a connectivity issue. Peace! ✌️
Most users don't want to use Big Picture regardless.
Whatever you say...
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=3609159105
... regular mode only.
This is a valid observation about the practices of Internet service providers in general, but it logically contradicts the available evidence.
Consider this: an Internet service provider applies a policy of limiting bandwidth based on protocols or overall bandwidth usage, not based on which specific graphical user interface (GUI) a client displays locally. My ISP has no way of knowing whether I am in “desktop mode” or “Big Picture mode” — the data packets look the same to it.
If this were a speed throttling issue on the part of the ISP, switching to Big Picture mode would have no effect. The fact that my speed immediately increases after switching proves that the limitation is a local bottleneck on the client side (probably the load on the processor from the browser user interface) and not a limitation on the provider's side in the WAN.
So, fortunately, there is no need to call or update equipment — a simple software solution is enough! :)
P.S. And yes, I have already called several times and asked, and the answer to my question was always the same (it's a problem on Steam's side, not ours).
I never claimed that this is a universal solution that will work for everyone without exception. Computer configurations and software environments vary greatly.
However, this particular method helped me personally solve the problem when nothing else worked. I am simply sharing my findings to help others who may encounter the same problem. If it helps someone, great!
Thank you for sharing!
Have a nice day! :)