• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Pagefile use when having lots of ram

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: bsobel
He's refering to unnamed memory mapped files which are backed by the paging system.

This is still something the memory manager takes care of. And pagefile backed sections can also be backed by physical memory alone. This subject has been discussed in these forum before.
 
The whole 1.5x-2x amount of memory rule of thumb is absolutely wrong. The more memory you have, the smaller the pagefile you'll need, not the larger.

That being said, leave it on auto. It wont make a difference if you make it smaller manually, and it wont get any larger than default if it doesnt ever need to be.
 
The more memory you have, the smaller the pagefile you'll need, not the larger.

Not necessarily, the amount of pagefile required is related to the workload being placed on the computer. A computer with 64M of memory may require no pagefile as long as it's working set fits entirely within that 64M but a computer with 64G may require 64G of pagefile space if it's doing some huge simulation or something. Obviously you want to use the pagefile as little as possible so it's best to try and fit your workload into the amount of physical memory that you have but that's not always possible.
 
Can anyone point me to some benchmarks which prove that messing around with the page file makes the system quicker or more stable?
 
Originally posted by: Nothinman
The more memory you have, the smaller the pagefile you'll need, not the larger.

Not necessarily, the amount of pagefile required is related to the workload being placed on the computer. A computer with 64M of memory may require no pagefile as long as it's working set fits entirely within that 64M but a computer with 64G may require 64G of pagefile space if it's doing some huge simulation or something. Obviously you want to use the pagefile as little as possible so it's best to try and fit your workload into the amount of physical memory that you have but that's not always possible.

Of course, I'm just saying that the 1.5-2x rule of thumb is silly. All other things being equal, you wouldnt need as much pagefile if you had more than enough ram for the tasks at hand. With 4GB of ram for a general desktop, you probably wouldnt even need one at all, although certain programs can get a little fussy if you dont have one, so its just best to leave it alone.
 
Originally posted by: bsobel
Originally posted by: Rubycon
Originally posted by: bsobel

You really have a 192gb memory load on that system? Unless you do, this is just silly.

Yes - the vendor suggests 256GB of RAM.

What app are you running which is using 192gb of memory? If your actually using it and swapping that much your app would very slow and you should consider upgrading the memory on the box.


Probably hosting some type of database or a monitoring application of some type. We have a few 8-core servers in one of our tech hubs that holds 64 Gb of RAM in each and they both do census data. Believe me, it hogs up resources.
 
Originally posted by: pallejr
Originally posted by: bsobel
He's refering to unnamed memory mapped files which are backed by the paging system.

This is still something the memory manager takes care of. And pagefile backed sections can also be backed by physical memory alone. This subject has been discussed in these forum before.

Regardless of the memory size and pagefile size, in overcommitted systems applications can still come to the point that the memory manager's response from mmap() is NO. There aren't a heckuva lot of apps that can tolerate that.
 
Originally posted by: degibson

Regardless of the memory size and pagefile size, in overcommitted systems applications can still come to the point that the memory manager's response from mmap() is NO. There aren't a heckuva lot of apps that can tolerate that.

Sure, but that wasn't the point at all.
 
and i can see some of the points made here. but some of us home users who just do one thing at a time with plenty of ram, should be fine.
mine runs the same since i turned it off so far.
 
Back
Top