Budget. Not doing anything other than gaming mostly on the rig. 16GB can do it, but task-switching on 16GB is just right there on the border of being "just enough", and I switch a lot between apps while gaming, recording and web browsing. My VR rig is 16GB and switching between programs, although mostly it works, some games and apps consume more than that and the rig starts page-filing. 32GB is the sweet spot for me. 64GB or 128GB is if I wanna run Windows in a RAMDisk environment, but with that NVME M2's blistering speed, I dont need RAMDisk.

Do you disable pagefile with 32 GB RAM or just leave Windows to manage it? I noticed that even with 32GB RAM, Windows still use pagefile.

No problems if the game engine is competent enough to keep up with the monitor, massive tearing if it isn't. With your kind of framerates, enable FastSync (if you're running single card) or Adaptive V-Sync (if you're running multiple cards). Or use traditional V-Sync if the game doesn't affect your inputs and introduces lag. With every games, they need to be tweaked differently, there's no rule of thumb here........unless you're running G-Sync, that takes care of almost everything.

Bear in mind, some people aren't susceptible to tearing, they don't see it as obvious, or don't really mind tearing as they're "used" to it. Others can't stand it. Just like those who can't stand anything lower than 120hz and 144hz monitors while others are perfectly okay with 60hz.

Just arrived ready to be installed today.



32GB worth of DDR4 at 3200Mhz, and 512GB worth of NVME M2 running at 2.5GB/s read rate.

Do you disable pagefile with 32 GB RAM or just leave Windows to manage it? I noticed that even with 32GB RAM, Windows still use pagefile.

I left it as it is. I'm more worried with Windows page-filing because, the drive space it's taking the pagefile storage from, is from a RAID0 array of two 480GB SSDs. If anything happens during pagefiling and the array collapses, I lose both SSDs. Nothing so far, but prevention is better than regret later.

Some said you wont notice tearing if monitor at high refresh rate like 144Hz as it refresh so fast, tearing frame wont be noticeable.
  3200MHz RAM
  that M.2 SSD can read/write how fast ? I wonder when will you upgrade to PCI-E card type SSD 
I disabled it I think.
I donno what Windows and/or Chrome feeding on these day, without gaming my RAM usage will be 70-80% ( with 8 Chrome tabs opened ) on 8GB.

That Samsung 950 PRO M.2 has a read/write of 2500/1500 if not wrong. A more common 850 EVO has 540/520. So much powah!! Almost an instantaneous boot up on power

Some said you wont notice tearing if monitor at high refresh rate like 144Hz as it refresh so fast, tearing frame wont be noticeable.
  3200MHz RAM
  that M.2 SSD can read/write how fast ? I wonder when will you upgrade to PCI-E card type SSD 
I disabled it I think.
I donno what Windows and/or Chrome feeding on these day, without gaming my RAM usage will be 70-80% ( with 8 Chrome tabs opened ) on 8GB.

Ahaaaaah. Used to have 32GB on my old rig, so had pagefile disabled coz I think its just taking up disk space without contributing much to system performance. Never had any issues with low memory having 32GB RAM. Currently on 16GB so I still have pagefile enabled until I can upgrade to 32GB. Hiberfil.sys disabled in my rig and laptop. That's another space hogger. Don't need hibernate since booting from SSD is fast anyways.

That Samsung 950 PRO M.2 has a read/write of 2500/1500 if not wrong. A more common 850 EVO has 540/520. So much powah!! Almost an instantaneous boot up on power

2.5GB read, 1.5GB write, W10 bootup less than 3 seconds under UEFI, you cannot access BIOS unless you initiate it through software within Windows or through the BIOS reset button on the motherboard.
I should try disabling that "Hibernate" option too and see if it improves system memory usage.
It's the similar feel of leap forward when using SSD for the first time moving from HDD. File transfer so far, the transfer window just blinks!

I should try disabling that "Hibernate" option too and see if it improves system memory usage.

screen tearing of course.

isnt that only happen to 144hz monitor when fps is above 144 

As far as I know, Hibernate and the the hiberfil.sys file it creates does not effect system memory usage, but on disk storage space If you have hibernate enabled, and the PC goes into hibernation mode, Windows will save the state of the PC into hiberfil.sys, so that when Windows resume from hibernation, it will use this hiberfil.sys to restore Windows, which supposedly make the PC wakes up faster, Just that in the era of HDD, this helps, but I think when using SSD, the benefit is negligible since fresh boot Windows is fast anyway. I've seen hiberfil.sys take ups to around 20GB of my SSD drive last time, so I just disabled it. That's just too much premium space on SSD wasted (back then I only had 128 GB SSD, so even 10GB going to hiberfil.sys is space I can use to install apps). But if using HDD, I do recommend hibernate as PC wakes up faster compared to normal boot.

Example of hiberfil.sys and pagefile.sys taking up drive space.

2.5GB read, 1.5GB write, W10 bootup less than 3 seconds under UEFI, you cannot access BIOS unless you initiate it through software within Windows or through the BIOS reset button on the motherboard.
I should try disabling that "Hibernate" option too and see if it improves system memory usage.
It's the similar feel of leap forward when using SSD for the first time moving from HDD. File transfer so far, the transfer window just blinks!

I can imagine. Price is almost double too for similar 500gb capacity but Samsung's range is still one of the better (dare I say best?) one in the market based on RM per specs and capacity

Haha well said anyway been using SSD after 2 strong years

screen tearing occur either fps is lower or greater than ur monitor refresh rate. to fully eliminate tearing we need gsync or vsync

yea hibernate more useful for laptops when you are mobile and dont want to shutdown completely. i also disable it on desktop PCs since it's a space hogger and i only use sleep and rarely ever use hibernate.

32GB is prob enough to disable page file but i also read that it cannot be completely disabled, windows still uses a small portion. maybe it reserve for memory dumps when BSOD? another annoying one is the SuperFetch which is suppose to speed up applications startup by caching in RAM, with SSD it should be automatically disabled by Windows.

First thing first. Fast Sync option not available with SLI I've checked a couple of times. Only when I disabled SLI, the "Fast" option is available under Nvidia Control Panel Vertical Sync pull down tab option. Anyone else running Pascal SLI can confirm this?  stringfellowyour Titan X Pascal SLI how leh?

So had to do this this test with my GTX 1080 SLI disabled. I'm using Firestrike Custom Run, Graphic Test 1 only. 1080P, MSAA, others default. I monitored frametime using Fraps and my GTX 1080 reading on HWMonitor

Using Firestrike Setting Vsync Enabled

[attachmentid=7320841] [attachmentid=7320842]

Using Nvidia "Adaptive" Vsync (Firestrike Vsync Setting Disabled)

[attachmentid=7320843] [attachmentid=7320844]

Using Nvidia "Fast" Vsync (Firestrike Vsync Setting Disabled)

[attachmentid=7320845] [attachmentid=7320846]

MY PERSONAL OPINION

All three Vsync option did what Vsync is suppose to do that is "eliminate screen tearing" when GPU can put out more fps than the monitor refresh rate (in my case 60 Hz = 60 fps = target constant 16.7 ms frame time). The built-in and adaptive Vsync does that by limiting the GPU to churn out only 60 fps, matching my monitor 60 Hz refresh rate. Looking at the frame time graph, median line is flat at 16.7 ms.

Whereas as Nvidia said, Fast Vsync let the GPU ran maxed out, so fps is maxed out (above 100 fps), but I don't see any screen tearing because the GPU now, only sent 60 frames to the monitor (to match the monitor 60 Hz) and discard the rest of the other 40+ frames that it has rendered. Frame time move up and down but all are well below 16.7 ms, stayed closer to 10 ms.

Looking at the hardware monitoring, there's not much difference between using app built-in vsync or nvidia adaptive too. Firestrike Mon Graph, temp is just around 51C-52C, and GPU load at 77%-78% and my CPU only need to ran constantly 3.4 GHz (temp around 38C-39C). HwMon showed peak GPU power less then 70%. The Adaptive Vsync GPU load fluctuated slightly more than the built-in vsync, again correlates to how these 2 vsync works in a different way.

Whereas for Fast Vsync, temp went up to 62C-63C, GPU load 98%-99%, and at certain part of the test, my CPU too ran up to 4.2 GHz (temp to went up to 43C). GPU power as shown by HwMon peaked at 104%.

Firestrike bench does not test input lag, which what Fast Vsync was suppose to address. To avoid screen tearing, I'll personally stick to game Vsync or Nvidia's Adaptive Vsync. Unless I have a game which suffers severely from input lag or micro-stuttering and Fast Vsync can reduce this, I would avoid using Fast Vsync. The extra load and heat on the GPU and CPU is not worth it for me. And it feels like waste; render 100+ frames, only sent 60 to monitor, and discard the 40+ frames, is like 40% wastage. Anyway, even if I want to use Fast Sync now, I can't because I'm running SLI.

And here's the same test with Adaptive Vsync but with GTX 1080 SLI.

[attachmentid=7320919]
I guess the graph shows the monitoring for the 1st GPU only. Load only between 30% - 42%. At some point, even the CPU load drop to 2.8 Ghz.

Great analysis bro! That's why I usually hit the 90-100% on all cores in Doom which I normally don't when on vsync.