Установить 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.