• 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.

Question Looking to max out RAM

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

silverfang77

Junior Member
My PC is a PowerSpec G418: ASRock Fatal1ty Z170 Gaming K6 ATX LGA1151 Motherboard, G. Skill 16GB DDR4-3200 RAM.

The board can max out at 64 GB RAM. Would I be best served getting this: https://www.newegg.com/corsair-64gb...gb_ddr4-_-20-236-586-_-Product&quicklink=true
CORSAIR Vengeance LPX 64GB (2 x 32GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4 25600) Desktop Memory Model CMK64GX4M2E3200C16,
https://www.newegg.com/corsair-64gb...gb_ddr4-_-20-236-586-_-Product&quicklink=true
or this: https://www.gskill.com/product/165/...DDR4-3200MHz-CL16-18-18-38-1.35V64GB-(2x32GB)
Trident Z Neo DDR4-3200MHz CL16-18-18-38 1.35V
64GB (2x32GB).
https://www.newegg.com/corsair-64gb...gb_ddr4-_-20-236-586-_-Product&quicklink=true
Thank you.
 
VL is correct regarding the commit charge.

Commit charge is the virtual memory (physical+pagefile) what system guarantees that will be available to programs/processes . It's not physical memory in use.

Sysinternal got a RAMMap utility that shows how much physical memory is in use.


Humm, I guess I'll give this a try. Always thought the second number on commit charge is the ram + pagefile size and if you hit that you hit a wall unless your pagefile is set to auto.
 
Humm, I guess I'll give this a try. Always thought the second number on commit charge is the ram + pagefile size and if you hit that you hit a wall unless your pagefile is set to auto.
That's true too. But that doesn't invalidate what I said.

Basically, that second number on commit charge, is the current ceiling on the commit charge, that it can reach. That's the current total pageable physical RAM + pagefile that can be allocated. If you have auto-expanding pagefile set, the kernel will "grow" the pagefile once the ceiling is close to being reached.

Nifty tip, on "auto" pagefile, the most that it can grow to, at least in Win7 64-bit, is 3X physical RAM, thus giving you, at most, 4X Physical RAM size in virtual memory capacity. (1X Physical RAM, plus 3X Physical RAM capacity in pagefile.)
 
Back
Top