安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
When an application needs memory, that memory is immediately reserved as virtual memory. However, the memory space is *not* allocated as RAM before it is actually needed, i.e. read from or written to. The CPU and operating system take care of all that. Applications just reserve memory and then access the memory sooner or later.
So, that 4 GB consists of reserved memory that has not been actually needed yet.
The 10% difference you noticed is quite constant for CS (for some apps, the difference is much bigger - my Steam client shows right now 97 MB RAM, 215 MB VM).
It is also fine if some of the reserved memory is never actually needed. VM reservations are basically just advance bookings and carry very little cost.
I guess that is why they use the word "commit" rather than "allocate" with VM reservations.