[Memory] Add system_memory_stats_recorder_win.cc

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 45cc91f35052ca012e8f8b908028caeef06f442d..5fb63af363a21c02e004e2c1a7de75576fe8be70 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -16963,6 +16963,71 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="Memory.Stats.Win.AvailPageFile" units="MB">
+  <owner>georgseak@chromium.org</owner>
+  <summary>
+    Windows-only metric that represents the maximum amount of memory the current
+    process can commit. This value is equal to or smaller than the system-wide
+    available commit value.
+  </summary>
+</histogram>
+
+<histogram name="Memory.Stats.Win.AvailPhys" units="MB">
+  <owner>georgseak@chromium.org</owner>
+  <summary>
+    Windows-only metric that represents the amount of physical memory currently
+    available. This is the amount of physical memory that can be immediately
+    reused without having to write its contents to disk first. It is the sum of
+    the size of the standby, free, and zero lists.
+  </summary>
+</histogram>
+
+<histogram name="Memory.Stats.Win.AvailVirtual" units="MB">
+  <owner>georgseak@chromium.org</owner>
+  <summary>
+    Windows-only metric that represents the amount of unreserved and uncommitted
+    memory currently in the user-mode portion of the virtual address space of
+    the calling process.
+  </summary>
+</histogram>
+
+<histogram name="Memory.Stats.Win.MemoryLoad" units="percent">
+  <owner>georgseak@chromium.org</owner>
+  <summary>
+    Windows-only metric that represents the approximate percentage of physical
+    memory that was in use (0 indicates no memory use and 100 indicates full
+    memory use).
+  </summary>
+</histogram>
+
+<histogram name="Memory.Stats.Win.TotalPageFile" units="MB">
+  <owner>georgseak@chromium.org</owner>
+  <summary>
+    Windows-only metric that represents the current committed memory limit for
+    the system or the current process, whichever is smaller.
+  </summary>
+</histogram>
+
+<histogram name="Memory.Stats.Win.TotalPhys" units="MB">
+  <owner>georgseak@chromium.org</owner>
+  <summary>
+    Windows-only metric that represents the amount of actual physical memory.
+  </summary>
+</histogram>
+
+<histogram name="Memory.Stats.Win.TotalVirtual" units="MB">
+  <owner>georgseak@chromium.org</owner>
+  <summary>
+    Windows-only metric that represents the size of the user-mode portion of the
+    virtual address space of the calling process. This value depends on the type
+    of process, the type of processor, and the configuration of the operating
+    system. For example, this value is approximately 2 GB for most 32-bit
+    processes on an x86 processor and approximately 3 GB for 32-bit processes
+    that are large address aware running on a system with 4-gigabyte tuning
+    enabled.
+  </summary>
+</histogram>
+
 <histogram name="Memory.Swap.Browser" units="KB">
   <owner>hajimehoshi@chromium.org</owner>
   <owner>kenjibaheux@google.com</owner>