SepelaThons 2018년 2월 14일 오전 12시 20분
Will virtual memory increase gaming performance?
Title
< >
25개 댓글 중 16-25개 표시
xSOSxHawkens 2018년 2월 14일 오후 7시 07분 
I generaly try to avoid just flat out telling people they are wrong... But here goes...

TL:DR Opening - most of what BadMotha has posted in the last two posts is factualy incorrect, and poor advice, this reply aims to clear up the bad information and provide a source for verification.

Bad_Motha님이 먼저 게시:
You don't even need a PageFile, period... install more RAM PageFile of around 1GB is all you will ever need.

Wrong, watch the linked vid that explains why. Short answer, there are still many apps that use, some that *require* and OS level functions that are dependent on or supported by the Pagefile evem on modern systems.

Also pagefile should always be able to accomodate the size of installed ram for system memory dumps. Period. Anything less than system ram size will cause windows to fail to be able to dump memory on system crash. Period.

Recomended (both by MS and as an industry standard) is 1.5-2x installed system RAM.

Bad_Motha님이 먼저 게시:
...but yea you don't really need anything set for PageFile; in fact wipe out whatever WinOS sets for that and set it yourself.

Partially wrong, and paritally conditionally correct. As alreaady explained (and suppoted by relevant source video at bottom) a page file is neccisary. As for your advice on chaning it form windows, conditionally correct. If one knows enough to change it to begin with they should have it set manualy and split across drives (again as explained in the source video), but if once does not know how to handle it letting windows manage the settings is acceptable, if not preffered.

Bad_Motha님이 먼저 게시:
And always to C drive, never to any other drive, period.
Mostly incorrect. You should *always* have a C: Drive Page File present, as in the event of a system crash the system can only dump to C drive, and any other drives, page file or not, will be ignored. Therefore you do always want a C drive page. That said, for actual performance a C drive page is very useless, as any information that is on the drive will conflict with its ability to page simultaionously. This is the exact reason it is HIGLY RECOMENDED as an industry standard to have TWO DRIVES each with their own page, and with half or more of the page on the secondary drive not primary...

Bad_Motha님이 먼저 게시:
Oh you have an SSD as your OS Drive, yea so what... it's not going to hurt the drive one bit.
This is actually correct. +10 points :)

Bad_Motha님이 먼저 게시:
You have to basically go back to non-NT Windows OS is really when PageFile was needed.
False, modern OS's highly utilise the page or swap files. Windwos, OSX, and Linux all make goodf use of Swap/Page files for OS level and Application level services.


Bad_Motha님이 먼저 게시:
Apps that still uses this after Win98/ME were just lazy devs to be honest, cause it wasn't need to make an app use PageFile, nor is it really a good thing that you write an app that forces the use of the PageFile.
Again, not at all true. In modern usage the page file gets used more as a dumping ground for data already present in system RAM when an application is launched that requires high RAM usage. You are correct that few programs write programs that directly access page files, but those that DO are not sloppy, unless you consider high level programs like Adobe's creation suites to be crappily written. In most cases is not about a specific app requiring the page, its about it wanting RAM, and the OS using the page to clear the RAM for you, but allowing a faster recovery into RAM of the cleared data than would be available in the case of a hard fault to the disk.

Bad_Motha님이 먼저 게시:
PageFile was more helpful overall on 32-bit OS due to the lack of allowed max physical RAM; now that isn't a problem, use 64-bit OS and just install whatever RAM you need..

Yes and no... I have seen mutipole systems that run 32bit Windows 10 (I own one myself) that still fall under the memory restrictions, and there are many systems that ship to consumers with 64bit OS and hardware and yet still have 2 or 4GB ram in them.

Even with 8GB ram, in a gaming or productivity situation, a large page is both wanted and needed. Modern titles can take upwards of 5-8GB of system RAM and in doing so will dump all information in RAM at time of launch to an available page.

In a multi page system (multi HDD) it will dump to whichever page has the lowest que, and sometimes to both at once.



https://youtu.be/1VDP5TCAK2c


^^^Please take 5 minutes to properly educate yourself on page files^^^



TL:DR Closing - Its a bad idea to follow advice advocating diabling page files or having them smaller than the installed system RAM. Page files are there for a reason, many actually, and just because some randome person on the net was able to disable theirs does NOT mean that it wont break things on your system, or visa-vera. More over, where there is NO negative effect (aside from losing a chunk of HDD/SSD space) to having a proper Page File, there are indeed MANY well documented ill-effects of disabling your page.

Just because it has wortked for you, BadMotha, does NOT mean you should advise or advocate others to do something that is widely accepted as BAD practice. Its like telling someone to go delete a randome file in win32 just because you got away with deleting the same thing and it didnt crash the system. Bad advice. Period.
Bad 💀 Motha 2018년 2월 14일 오후 9시 19분 
xSOSxHawkens님이 먼저 게시:
I generaly try to avoid just flat out telling people they are wrong... But here goes...

TL:DR Opening - most of what BadMotha has posted in the last two posts is factualy incorrect, and poor advice, this reply aims to clear up the bad information and provide a source for verification.

Bad_Motha님이 먼저 게시:
You don't even need a PageFile, period... install more RAM PageFile of around 1GB is all you will ever need.

Wrong, watch the linked vid that explains why. Short answer, there are still many apps that use, some that *require* and OS level functions that are dependent on or supported by the Pagefile evem on modern systems.

Also pagefile should always be able to accomodate the size of installed ram for system memory dumps. Period. Anything less than system ram size will cause windows to fail to be able to dump memory on system crash. Period.

Recomended (both by MS and as an industry standard) is 1.5-2x installed system RAM.

Bad_Motha님이 먼저 게시:
...but yea you don't really need anything set for PageFile; in fact wipe out whatever WinOS sets for that and set it yourself.

Partially wrong, and paritally conditionally correct. As alreaady explained (and suppoted by relevant source video at bottom) a page file is neccisary. As for your advice on chaning it form windows, conditionally correct. If one knows enough to change it to begin with they should have it set manualy and split across drives (again as explained in the source video), but if once does not know how to handle it letting windows manage the settings is acceptable, if not preffered.

Bad_Motha님이 먼저 게시:
And always to C drive, never to any other drive, period.
Mostly incorrect. You should *always* have a C: Drive Page File present, as in the event of a system crash the system can only dump to C drive, and any other drives, page file or not, will be ignored. Therefore you do always want a C drive page. That said, for actual performance a C drive page is very useless, as any information that is on the drive will conflict with its ability to page simultaionously. This is the exact reason it is HIGLY RECOMENDED as an industry standard to have TWO DRIVES each with their own page, and with half or more of the page on the secondary drive not primary...

Bad_Motha님이 먼저 게시:
Oh you have an SSD as your OS Drive, yea so what... it's not going to hurt the drive one bit.
This is actually correct. +10 points :)

Bad_Motha님이 먼저 게시:
You have to basically go back to non-NT Windows OS is really when PageFile was needed.
False, modern OS's highly utilise the page or swap files. Windwos, OSX, and Linux all make goodf use of Swap/Page files for OS level and Application level services.


Bad_Motha님이 먼저 게시:
Apps that still uses this after Win98/ME were just lazy devs to be honest, cause it wasn't need to make an app use PageFile, nor is it really a good thing that you write an app that forces the use of the PageFile.
Again, not at all true. In modern usage the page file gets used more as a dumping ground for data already present in system RAM when an application is launched that requires high RAM usage. You are correct that few programs write programs that directly access page files, but those that DO are not sloppy, unless you consider high level programs like Adobe's creation suites to be crappily written. In most cases is not about a specific app requiring the page, its about it wanting RAM, and the OS using the page to clear the RAM for you, but allowing a faster recovery into RAM of the cleared data than would be available in the case of a hard fault to the disk.

Bad_Motha님이 먼저 게시:
PageFile was more helpful overall on 32-bit OS due to the lack of allowed max physical RAM; now that isn't a problem, use 64-bit OS and just install whatever RAM you need..

Yes and no... I have seen mutipole systems that run 32bit Windows 10 (I own one myself) that still fall under the memory restrictions, and there are many systems that ship to consumers with 64bit OS and hardware and yet still have 2 or 4GB ram in them.

Even with 8GB ram, in a gaming or productivity situation, a large page is both wanted and needed. Modern titles can take upwards of 5-8GB of system RAM and in doing so will dump all information in RAM at time of launch to an available page.

In a multi page system (multi HDD) it will dump to whichever page has the lowest que, and sometimes to both at once.



https://youtu.be/1VDP5TCAK2c


^^^Please take 5 minutes to properly educate yourself on page files^^^



TL:DR Closing - Its a bad idea to follow advice advocating diabling page files or having them smaller than the installed system RAM. Page files are there for a reason, many actually, and just because some randome person on the net was able to disable theirs does NOT mean that it wont break things on your system, or visa-vera. More over, where there is NO negative effect (aside from losing a chunk of HDD/SSD space) to having a proper Page File, there are indeed MANY well documented ill-effects of disabling your page.

Just because it has wortked for you, BadMotha, does NOT mean you should advise or advocate others to do something that is widely accepted as BAD practice. Its like telling someone to go delete a randome file in win32 just because you got away with deleting the same thing and it didnt crash the system. Bad advice. Period.


No. You just turn it off, and done...

It will use it if it's on. If you have plenty of RAM, you don't need it.
Oh..... I've been running all my PCs this way since around the time Win7 came out, but I'm guess i'm wrong right? :steamfacepalm:
Astro_80 (WASH YOUR HANDS!) 2018년 2월 14일 오후 10시 49분 
Bad_Motha님이 먼저 게시:
xSOSxHawkens님이 먼저 게시:
I generaly try to avoid just flat out telling people they are wrong... But here goes...

TL:DR Opening - most of what BadMotha has posted in the last two posts is factualy incorrect, and poor advice, this reply aims to clear up the bad information and provide a source for verification.



Wrong, watch the linked vid that explains why. Short answer, there are still many apps that use, some that *require* and OS level functions that are dependent on or supported by the Pagefile evem on modern systems.

Also pagefile should always be able to accomodate the size of installed ram for system memory dumps. Period. Anything less than system ram size will cause windows to fail to be able to dump memory on system crash. Period.

Recomended (both by MS and as an industry standard) is 1.5-2x installed system RAM.



Partially wrong, and paritally conditionally correct. As alreaady explained (and suppoted by relevant source video at bottom) a page file is neccisary. As for your advice on chaning it form windows, conditionally correct. If one knows enough to change it to begin with they should have it set manualy and split across drives (again as explained in the source video), but if once does not know how to handle it letting windows manage the settings is acceptable, if not preffered.


Mostly incorrect. You should *always* have a C: Drive Page File present, as in the event of a system crash the system can only dump to C drive, and any other drives, page file or not, will be ignored. Therefore you do always want a C drive page. That said, for actual performance a C drive page is very useless, as any information that is on the drive will conflict with its ability to page simultaionously. This is the exact reason it is HIGLY RECOMENDED as an industry standard to have TWO DRIVES each with their own page, and with half or more of the page on the secondary drive not primary...


This is actually correct. +10 points :)

False, modern OS's highly utilise the page or swap files. Windwos, OSX, and Linux all make goodf use of Swap/Page files for OS level and Application level services.



Again, not at all true. In modern usage the page file gets used more as a dumping ground for data already present in system RAM when an application is launched that requires high RAM usage. You are correct that few programs write programs that directly access page files, but those that DO are not sloppy, unless you consider high level programs like Adobe's creation suites to be crappily written. In most cases is not about a specific app requiring the page, its about it wanting RAM, and the OS using the page to clear the RAM for you, but allowing a faster recovery into RAM of the cleared data than would be available in the case of a hard fault to the disk.



Yes and no... I have seen mutipole systems that run 32bit Windows 10 (I own one myself) that still fall under the memory restrictions, and there are many systems that ship to consumers with 64bit OS and hardware and yet still have 2 or 4GB ram in them.

Even with 8GB ram, in a gaming or productivity situation, a large page is both wanted and needed. Modern titles can take upwards of 5-8GB of system RAM and in doing so will dump all information in RAM at time of launch to an available page.

In a multi page system (multi HDD) it will dump to whichever page has the lowest que, and sometimes to both at once.



https://youtu.be/1VDP5TCAK2c


^^^Please take 5 minutes to properly educate yourself on page files^^^



TL:DR Closing - Its a bad idea to follow advice advocating diabling page files or having them smaller than the installed system RAM. Page files are there for a reason, many actually, and just because some randome person on the net was able to disable theirs does NOT mean that it wont break things on your system, or visa-vera. More over, where there is NO negative effect (aside from losing a chunk of HDD/SSD space) to having a proper Page File, there are indeed MANY well documented ill-effects of disabling your page.

Just because it has wortked for you, BadMotha, does NOT mean you should advise or advocate others to do something that is widely accepted as BAD practice. Its like telling someone to go delete a randome file in win32 just because you got away with deleting the same thing and it didnt crash the system. Bad advice. Period.


No. You just turn it off, and done...

It will use it if it's on. If you have plenty of RAM, you don't need it.
Oh..... I've been running all my PCs this way since around the time Win7 came out, but I'm guess i'm wrong right? :steamfacepalm:

Yes, you are wrong. Watch the video as suggested.
Bad 💀 Motha 2018년 2월 14일 오후 11시 03분 
You still don't need it, that's why you can turn it off :steamfacepalm:
How hard is to understand this? Learn your OS and how it works. Stop watching junk videos.
Bad 💀 Motha 님이 마지막으로 수정; 2018년 2월 14일 오후 11시 04분
xSOSxHawkens 2018년 2월 14일 오후 11시 16분 
Bad_Motha님이 먼저 게시:
You still don't need it, that's why you can turn it off :steamfacepalm:
How hard is to understand this? Learn your OS and how it works. Stop watching junk videos.
Stop spreading bad advice...

Can you turn it off and *maybe* be OK? Yes...

Does ANYONE who has actual credible knowledge or professional experiance in this industry SUGGEST it? No they do not.

MS says its bad to turn off...

Any major productivity devs on the planet (Adobe, Maxxon, Etc) say its bad to turn off...

Many game devs have gone on record over the years saying its needed and essential for proper game fucntionality....



Just because it works for YOU does NOT mean its OK advice to give to everyone...

Dont spread PERSONAL advice as if its correct when you KNOW that it goes against any and ALL industry practice...


At the very least take responsibility for the FACT that you are spreading an opinion from personal experiance, and let people KNOW that despite it wokring OK for you it is NOT whats recomended by microsoft and they should proceed at their own risk.
Bad 💀 Motha 2018년 2월 15일 오전 12시 43분 
xSOSxHawkens님이 먼저 게시:
Bad_Motha님이 먼저 게시:
You still don't need it, that's why you can turn it off :steamfacepalm:
How hard is to understand this? Learn your OS and how it works. Stop watching junk videos.
Stop spreading bad advice...

Can you turn it off and *maybe* be OK? Yes...

Does ANYONE who has actual credible knowledge or professional experiance in this industry SUGGEST it? No they do not.

MS says its bad to turn off...

Any major productivity devs on the planet (Adobe, Maxxon, Etc) say its bad to turn off...

Many game devs have gone on record over the years saying its needed and essential for proper game fucntionality....



Just because it works for YOU does NOT mean its OK advice to give to everyone...

Dont spread PERSONAL advice as if its correct when you KNOW that it goes against any and ALL industry practice...


At the very least take responsibility for the FACT that you are spreading an opinion from personal experiance, and let people KNOW that despite it wokring OK for you it is NOT whats recomended by microsoft and they should proceed at their own risk.

Well that's the thing; no one posts facts on why it's needed, Microsoft can't even do that.

The FACT is, it's a personal choice. Simple as that really.

Most things to do with anything we discuss here is personal preferences; that's kinda how all this works anyways.
tacoshy 2018년 2월 15일 오전 1시 01분 
yup I know that bad Motha does this for a living, I know other constant users here that do this for at least as a side job. And plenty of the users ehre are enthusiasts that build and test alot.

Well you said it yourself. Using pagefile does nothing with the FPS but load times...



xSOSxHawkens님이 먼저 게시:
Once loaded, it will do NOTHING for the frame rate (fps) of the game (though in some games might help with pop in).

To give an idea of performacne difference. On my secondary rig (Athlon II x4 @ 3.7Ghz, HD7870 at time of testing) with a single mechanical HDD and 6GB RAM, BF4 maps take upwards of 90 seconds to load, someitmes as much as 120+...

Same system with twin HDD and spluit pagefile drops loading down to consistently under 60 seconds.

Same system with cheap SSD and 16GB page file will load in an average of 30-40 seconds.

to quote yourself: Once loaded, which can take quite a while compared to having enough RAM in the first place.

With 16GB pagefile on SSD you have laodtimes of 30-40 sec in BF4. I just have 32GB RAM where only 13GB where used max in my last year without productive work. Laodtimes are normally below 5 seconds. Mostly nearly insteantly (2 sec or less).



So page file can tweak a bit to speed up things but it can not replace the RAM soley for the speed. you ahve a bit faster loadtimes which cant be called gaming experience. Installing the game on the SSD would be a more effective way. But gaming experience RAM wise has alot to do with the fps drops and so on aaswell as certain games liek ARMA III are RAM depending where pagefile wont help even closely.
xSOSxHawkens 2018년 2월 15일 오전 2시 07분 
tacoshy님이 먼저 게시:
yup I know that bad Motha does this for a living, I know other constant users here that do this for at least as a side job. And plenty of the users ehre are enthusiasts that build and test alot.

Well you said it yourself. Using pagefile does nothing with the FPS but load times...



xSOSxHawkens님이 먼저 게시:
Once loaded, it will do NOTHING for the frame rate (fps) of the game (though in some games might help with pop in).

To give an idea of performacne difference. On my secondary rig (Athlon II x4 @ 3.7Ghz, HD7870 at time of testing) with a single mechanical HDD and 6GB RAM, BF4 maps take upwards of 90 seconds to load, someitmes as much as 120+...

Same system with twin HDD and spluit pagefile drops loading down to consistently under 60 seconds.

Same system with cheap SSD and 16GB page file will load in an average of 30-40 seconds.

to quote yourself: Once loaded, which can take quite a while compared to having enough RAM in the first place.

With 16GB pagefile on SSD you have laodtimes of 30-40 sec in BF4. I just have 32GB RAM where only 13GB where used max in my last year without productive work. Laodtimes are normally below 5 seconds. Mostly nearly insteantly (2 sec or less).



So page file can tweak a bit to speed up things but it can not replace the RAM soley for the speed. you ahve a bit faster loadtimes which cant be called gaming experience. Installing the game on the SSD would be a more effective way. But gaming experience RAM wise has alot to do with the fps drops and so on aaswell as certain games liek ARMA III are RAM depending where pagefile wont help even closely.


You make the assumption that adding more RAM is always an option...

The backup system in question has only 6GB ram and the motherboard maxes at 8GB.

My motherboard, which is an MSI Mpower Z97 only supports up to 32GB...

You, using a machine *with* 32GB is an exception, NOT the norm. Most people have 4, 8, or perhaps 16GB unless they are content creators or have more money than brains.

You cannot compare anyone who is using 16+ GB ram with people who are on 8 and under in terms of the impact that a proper page file can make. Period.

And you cannot just expect people to shill out more money for faster load times, especialy if their system for what ever reason cant support more than they already have...

I have never argued againt having more ram, but it seems like I am one of the *only* people who can understand or comprehend that adding more ram is not always an option for one reason or another. In that case, especialy in that case, a proper page file is essential, and I have offered sound and industry standard advice.

As ususeual the proclaimed "enthusiasts" that have 32gb+ ram come along and claim its not needed. Its so common its cleche, and its been proven time and again flase. Even high RAM users need proper page files...

I did some IT support for a comany that was involved in trafic modeling. We deployed workstation class laptops with 64+GB ram and deployed desktops that had upwards of 128GB ram and xeons, and those ALL had properly configured (1.5-2x RAM) pagefiles...

Why? Because when you USE your ram to its limit, no matter HOW much, you need a page file. Period. You try and simulate millions of pedestrians cars and such, you need ram and page.
tacoshy 2018년 2월 15일 오전 2시 16분 
oh we get that not everybody can afford 16GB RAM. But the original question was if it will improve gaming performance. You said it yourself, besides load times it doesnt. Gaming performance mostly is not load times. So like I said it is minor tweaking but not replacing RAM or really improve gaming performance that is cause by missing RAM.

What you basically do is using a RAM cache while dumping the RAM cache back to the drive.

IMO there is no way aroudn to make up for missing RAM then getting enough RAM. Modern titles requiring more then 8GB RAM do not run well anyways on platforms not supporting more then 8GB RAM. Load times you dont speed up with pagefile ramdisc but just installing or move the game on a SSD in the first palce or using something dedciated as cache like Intel optane or small used SSD.
tacoshy 님이 마지막으로 수정; 2018년 2월 15일 오전 2시 22분
xSOSxHawkens 2018년 2월 15일 오전 3시 54분 
I guess it comes down to what you consider game performance...

For me load times are a definant part of game performance. Take games such as GTA-V or FO4, both of which will run fine FPS wise on a traiditonal HDD and 4GB ram, so long as you are fully loaded into the area of play. But both thos games are known to have *many* loading screens that are known to be long even on decent systems.

In such a case, a single HDD 4GB system would be a nightmare to play either game on. You would get windows of playability followed by minutes of loading....

On the flip side, a 4GB system with two HDD and a split page would cut loading times by half, and an SSD page on a small boot SSD with games on a secondary HDD would drop them another large chunk.

Sure, they could install the game to an SSD, if they have one big enough. And they can add more RAM, if they have the money.

But those are two direct examples of games where the *overal* game experiance can and will be improved by a proper page file on a system that meets but does not exceed requirements.

Simply put, FPS does not equal the definition of "gaming performance"... It might be all thats needed for single map games, but load times are just as important of a factor in certain games in terms of overal impact on the game session.
< >
25개 댓글 중 16-25개 표시
페이지당 표시 개수: 1530 50

게시된 날짜: 2018년 2월 14일 오전 12시 20분
게시글: 25