This might be a fun one to discuss... I'm not even sure this is problematic or no big deal at all. I'm leaning towards no big deal. I bring it up because the behavior is unlike any other server I have (though that doesn't necessarily mean it's wrong/bad).
I have a physical server running Windows 2012 R2 with 24GB of physical memory. Paging file is set to be managed by the OS and is currently 4.58GB in size. The server is not heavily used. What's strange is, the server's paging file usage is constantly upwards of 90% -- which is unlike any other servers I manage, including servers that are running on the -same- hardware spec, -same applications-, etc. The server in question with the 90%+ paging file usage is a bit of an anomaly. Few things to note... 1. The server's Committed Bytes is always hovering around 12GB or so... which is way below the Commit Limit (I think is 28GB or so, (physical memory + virtual memory)). So that seems to be completely normal. 2. The server's Page Faults/sec and Pages/sec are nearly identical with other servers I have that are serving up the same roles/functions and with the same hardware specs. So that also seems completely normal. 3. The server's Available Memory is always around 50%. So that also seems to be completely normal. 4. Because of the 90% Paging File Usage, the server's c: drive "Disk Write Time %" is noticeably higher (averaging around 20% utilization) than other servers (which average around 3% utilization), but it's obviously not high enough that it's affecting performance. I'd also expect to see higher Disk Write Time % with a more heavily utilized Page File anyways. 5. The server's Paging File Usage hovers around 90% (a reboot will lower it temporarily but will return back to 90% after 2-3 days) continually. The other servers I have that are serving up the same roles/functions and with the same hardware specs usually show around 0-10% Paging File Usage. Big difference. 6. The paging file itself, seems to be used, as far as process/bytes go, by SQL (there's a very -small- app using SQL on the box) and also by Java. However, nearly identical servers with the same apps (and SQL too) and hardware specs, don't show the same high Paging File Usage results. All in all, there's seemingly nothing wrong, but it bugs me that the Page File Usage on this particular server is so high. It SEEMS like perhaps there's just something wonky with the SQL and/or Java apps on this particular box that are using the Pagefile so much versus numerous other similar servers... I guess I'm curious... Would any else bother spending the time to figure out what's going on with the Pagefile? Ha. Like I said, there's no real performance hits or problems so maybe it'd be a waste of time, except for figuring it out for curiosity's sake. Jesse Rink Source One Technology, Inc. HP Partner 262 993 2231 ** Please visit our blog! http://www.sourceonetechnology.com/blog/
