Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Normas y directrices sobre discusión
Denunciar este mensaje
Manual pagefile handling is a holdover from The Olden Days(tm) where the worst thing to happen during a game was Windows running out of virtual memory and hurriedly grabbing more disk space for the pagefile. This would lag out the game and leave you with a terribly constructed, highly fragmented pagefile which just causes more issues than it was worth.
These days it's extremely rare for Windows to have to dynamically resize the pagefile on the fly, and drives are bigger and faster so even if it does it's not as much of an issue.
If you want to make a proper change to PageFile; first set it to NONE and SET. Click OK on both windows and then reboot the system to apply the change. Then if you want it on Auto / OS Managed, now set it to this. Be sure to click SET when making any change. Then again click OK on both windows and then restart the system to apply the change.
Your issue here though could have easily been some sort of RAM related issue or a random crash with the game.
Pagefile according to most people here they really don't understand how pagefile actually works. Pagefile is also known as swap-file on Linux as a result are mostly equivalent. Pagefile is intended to map virtual memory to physical memory, most systems have a largely finite store of RAM as a result pagefile is used to store pages in blocks usually 4KB at a time or larger in the form of memory segments. The reason pagefile impacts game performance is due to a process called asset paging in this situation the game will pull up from disk assets such as models, textures, and other data that the game may need in future, this is then put into a queue and this queue is maintained by the Translation Look Aside buffer and the pagefile translation table, this is a dedicated part of the CPU to improve access times by providing a cache containing the most recent pagefile accesses. Which reduces the access time to virtual memory translations. Pagefile is necessary as it's often a place programs will use for temporary storage of information that isn't required exactly right now.
Leaving the pagefile on automatic is often a good idea in regards to windows but you can set it to equal your RAM, which will mostly ensure the pagefile will never grow beyond a certain point. Pagefile is also a safe-guard against memory leakage. Because if your main physical memory addresses fill up beyond their capacity the system will not start swapping memory blocks out (evicting them) if the pagefile is active, this is actually very slow if the system has to start doing this, this is why it's NOT a good idea to disable your pagefile, the system needs it a lot of the time. Some applications will also use the pagefile as a "scratch disk" Adobe Photoshop and Illustrator are two examples that do this.
So further explain this concept VM (Virtual memory) is translated into physical memory address space. So if you have 64GB of physical memory and another 64GB of virtual memory you have a total of 128GB of memory. But after the 64th GB memory starts getting mapped to the disk (pagefile) So every "byte"of memory after the 64th gigabyte or the last address in the byte addressable space.
Most people here have a rudimentary understanding of how the virtual memory works.
Increasing the Pagefile size will only lower your free space of your drive, but in return will help with performance in a way, especially if your Pagefile size is low.
And I would recommend against from using HDD as Pagefile, because depending on the game and how much data is being removed and added into the Pagefile. The Pagefile can eventually choke up the HDD, which potentially affect the performance of the game (more noticeable, slower load times or longer asset/texture streaming time) as there could be a backlog of data that is queued up to be stored or removed from the Pagefile, due to the game.
But again, the benefits and the affects of having your Pagefile on an HDD is wholly dependant on:
A. The game and the amount of data that is continuously being written or removed from the Pagefile by the game.
B. The storage option you used for Pagefile. HDD is fine, until the game consistently writes and removes moderate size of data from the Pagefile.
As a final note; it does not matter if you have loads of RAM/Memory available, games will always use VM/Pagefile. How much is up to the game itself.
https://docs.microsoft.com/en-US/windows/client-management/determine-appropriate-page-file-size
Some quotes, with bold emphasis done by me.
That final statement says it all. There is no one size fits all answer
You would have to go through a process to determine what that need is for your own system with your own uses, and Process Explorer can help here (if your uses ever change, so does what you need!). I remember back in the late 2000s there was a lot of good information about this you could find, with this being one example...
https://web.archive.org/web/20130118041656/http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx
While some systems indeed are able to get by with minimal/no page file, the advice that all others should do this is careless, and the idea that you should adjust it, or that having the page file is a huge detriment to general performance by being enabled, isn't backed by evidence. You run into risks by restricting (setting a small and/or static size) or disabling it, and care should be taken before doing so by knowing what your needs are and that you don't need it (most just follow this advice because they've seen it for years and when they don't run into issues they presume it's one of those performance tricks they must do, but most simply get by because they have far more RAM than their use case usually needs). Again, if it works for you, that's fine, and I'm not telling anyone how to set their system, but giving advice about how it's a good practice is rather careless as it is very much system and use dependent so you open yourself up to risks by disabling without knowing if you may need it. I say that as someone who took that advice long ago and then later discovered the potential implications.Yes, myself included. I learned the hard way, which is why I no longer consider this some "performance tweak" with some predefined values to use that must be done to improve Windows.