安装 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(越南语)
Українська(乌克兰语)
报告翻译问题



Compare Steam & the other software against the core readout in Task Manager's Performance tab. Steam and Task Manager should correspond.
Excellent, thank you !
I does indeed appear as if the Steam Perf Mon is drawing all of it's CPU related statistics right from windows task manager. Which is both good, and bad unfortunately :(
While task manager is accurate in most of it's readouts - unfortunately there is a fairly well known bug with task manager's clock speed value - where it's using the wrong info (FSB, Multiplier, etc) to calculate the live clock speed, and thus gives an incorrect valve.
This is easily verified by checking task manger's clock speed value against something like HWinfo or AIDA64.
So if you are seeing a clock speed value in Steam Perf Mon that's either lower than you'd expect, or higher than your boost speed should go - it's likely just that your task manager is bugged.
Steam is literally just calling the windows API for this. Not sure what you want steam to 'fix' if Task Manager, a literal Windows tool does the same thing. Also non-technical people facing tools tend to smooth out data so that it doesn't look insanely noisy, as most of the time they don't need mili-second levels of accurate data.