Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
You went way over detail for most people, as most people aren't techies then they won't care to read all that information (AKA TL;DR). These days, most OSs aren't as dependent on virtual memory as they use to but as you said, still not a great idea to disable it because some processes may still refer directly to virtual memory rather than RAM and of course it risks OOMing.
Only enable it when I specifically need log files for troubleshooting something.
Great... and that has done what for your system... it really supplies no real worthwhile benefits.
Let em run an unstable computer. Anybody with a computer period who claims to never have issues is flat out lying. In this case we just know what the cause probably is for their random freezes and lockups.
I swear the level of computer illiteracy in PC gamers is stunning.
For one it prolongs the life of SSD's and 2, RAM has much faster read/wright and access times then even PCIE SSD's.
A game like GTA that streams from your storage device... It helps to take the load away from it and put it on RAM.
Furthermore, some page file info are outdated.
Page file configuration are not that critical in home PC but more for enterprise stability where you need to enable the page file for crash dump analysis in case of an OS crash.
I have personally disabled my page file for 'performance reasons' for years as I have more than sufficient RAM and has been trouble free...
Translation: I dont understand how hardware or software works.
Textures are not loaded from the pagefile... They are loaded directly from the game folder on the HDD/SDD. Any benefit you think you are getting is purely in your own head.
The placebo effect is a hell of a thing.
If after reading this you still want to mess with your systems stability, be my guest and mess with or disable your pagefile. Im done trying to point out the lies and ♥♥♥♥♥♥♥♥.
Well, as we here can see your a total noob on this. I installed games on RAM DISK... I know you don't even know what that is... But you should look it up.
Textures are streamed from storage to RAM/VRAM. This game is 65 GB and there is no way your going to store 65 GB in a page file or 8 or even 16 GB of RAM.
But hey, noobs believe what they wanna believe. Like I said, 3+ years... No page file and I have had zero issues.
While I commend you on having a well writen and *mostly* factual post, this part deserves to be brought out as false (some times).
Windows auto-managing of the page file is a great option for many, especialy all of the non-gamer PC users. But windows will NOT manage the PageFile correctly for a system with greater than around 4GB, as it makes the PageFile too small by default.
For gamers, and those that are heavy on their ram usage, the officialy Microsoft Recomendation for PageFile size has always been a 1:1 ratio with ram. However, though that is the official written advice from MS, it is NOT how the system will auto-alocate. For 4GB and above users it will generaly only make a PageFile fo about half the amount of ram.
This can have very REAL performance impacts on Gamers, especialy those in the sub-8GB ram range.
Take me for example, I have 6GB ram (2x2, 2x1). My system had an auto-managed page file of 4GB for about a year after installing the OS. One weekend I downloaded the free weekebd of CoD - Advanced Warfare, which is an INSANE memory hog (far more than any GTA).
With the game on minimum settings @ 720P it used 4.8GB of ram, and litteraly forced windows to push all my OS data into the Pagefile. When I tried to load into any matches though, it would crash to desktop without an error listed.
I manualy upped my Page File by 2GB to bring it to a 1:1 of 6GB ram and 6GB page file, now when I ran the game the pagefile was filled up even more, and the game used about 5.4gb of ram and loaded the missions.
The Auto-Managed Page file was not enough to dump the memory, and the game needed more. Only by manualy controlling the PageFile and setting it to the recomended MS value of 1:1 was I able to attain stability in my game.
Just like in the example above, there are MANY times when increasing your pagefile over the default is better than not, especialy when dealing with data intesive apps.
same here , on 3 different systems , with all over 32gigs of ram , never had an issue or system instability because of the no pagefile..
Windows not updating it's settings to reflect hardware changes is one of the times where manually changing the pagefile/virtual memory settings is correct. Mostly when increasing the amount of RAM your system has.
Of course for the added benefit of not having to use perfmon to detect that memory leak... you are more vulnerable to an OOM from said memory leak, just saying. Virtual Memory doesn't lead to decreased performance if it isn't doing anything, it only leads to decreased performance if you are heavily paging which only occurs because you are low on free memory and would OOM else wise anyways... with modern RAM. To avoid this problem you just tossed lots of RAM at the machine in the hope you never use it all.