2 files | articles.json, 3462-CD4C-36BD-5767-understanding-the-in-game-overlay-performance-monitor.txt

Author: SteamDB-Tracker

articles.json

@@ -866,8 +866,8 @@
     "3774805164909483879": {
         "title": "Understanding the In-Game Overlay Performance Monitor",
         "url_code": "3462-CD4C-36BD-5767",
-        "version": 3,
-        "timestamp": "2025-06-23 17:35:20"
+        "version": 4,
+        "timestamp": "2025-08-07 22:36:45"
     },
     "3786589850087740482": {
         "title": "Steam Guard: How to remove my mobile authenticator from the mobile app",

docs/3462-CD4C-36BD-5767-understanding-the-in-game-overlay-performance-monitor.txt

@@ -12,9 +12,9 @@ Let's dive into the detailed meaning of each section that might be displayed dep
 
 [h2]FPS + DLSS/FSR Frame Generation[/h2]
 
-FPS means frames per second, and is a common gaming performance metric.  It represents how many times the game can run, update it's world simulation, process input, generate a new back buffer image, and present it to the monitor.  Most gamers are used to thinking of FPS as a single number and have some rule in their head like 60 FPS feels smooth, anything 30-60 might be passable but is less good, and anything below 30 is really bad.  Competitive gamers might up their target to 120 or higher for ultra low latency and smooth response times.  However, on today's modern systems framerate has been complicated by the introduction of frame generation technology like DLSS and FSR.  If a user has a capable GPU and has frame generation turned on then most software will see the FPS number as including the generated frames.  This is correct if you think about just the smoothness of the video and how frequently the monitor is updated.  However, this is incorrect if you care about actual game frames, which do other work like process input, handle network updates, perform collision detection for models and projectiles, etc.  Frame generation can't help with things like input latency that matter to competitive gamers, but it can make things look visually smoother on todays high refresh rate monitors.
+FPS means frames per second, and is a common gaming performance metric.  It represents how many times in a second the game can run, update it's world simulation, process input, generate a new back buffer image, and present it to the monitor.  Most gamers are used to thinking of FPS as a single number and have some rule in their head like 60 FPS feels smooth, anything 30-60 might be passable but is less good, and anything below 30 is really bad.  Competitive gamers might up their target to 120 or higher for ultra low latency and smooth response times.  However, on today's modern systems framerate has been complicated by the introduction of frame generation technology like DLSS and FSR.  If a user has a capable GPU and has frame generation turned on then most software will see the FPS number as including the generated frames.  This is correct if you think about just the smoothness of the video and how frequently the monitor is updated.  However, this is incorrect if you care about actual game frames, which do other work like process input, handle network updates, perform collision detection for models and projectiles, etc.  Frame generation can't help with things like input latency that matter to competitive gamers, but it can make things look visually smoother on todays high refresh rate monitors.
 
-The Steam Performance monitor will detect frame generation technology and break down both the DLSS/FSR Frame Gen including FPS and the actual game FPS over 1 second intervals.  Further, the overlay will show the minimum and maximum single game frame performance within those one second intervals.  If you see a single FPS XX number plus the ↓Max↑Min, then your game is not actively using frame generation.  If you see a DLSS/FSR/FG number followed by FPS XX ↓Min↑Max, then your game is using frame generation actively and you get both that display frame rate including generated frames and the actual game frame rate.  Note that frame generation enabled games will commonly switch frame generation off in menus and cutscenes and that this is normal and correct behavior to see.
+The Steam Performance monitor will detect frame generation technology and break down both the DLSS/FSR Frame Gen including FPS and the actual game FPS over 1 second intervals.  Further, the overlay will show the minimum and maximum single game frame performance within those one second intervals.  If you see a single FPS XX number plus the ↓Min↑Max, then your game is not actively using frame generation.  If you see a DLSS/FSR/FG number followed by FPS XX ↓Min↑Max, then your game is using frame generation actively and you get both that display frame rate including generated frames and the actual game frame rate.  Note that frame generation enabled games will commonly switch frame generation off in menus and cutscenes and that this is normal and correct behavior to see.
 
 [b]A note on micro stutter: [/b] Users sometimes experience a solid average frame time, say 60-70 FPS, but will complain a game feels bad and that the frame rate drops now and then even though the FPS Avg doesn't reflect it.  At Valve we refer to this as micro stutter.  What happens, is that even if your game frequently runs at a solid 70 FPS, one single long frame that takes much more time than others can cause a visible stutter or input latency that you notice.  We have given you the ↓Min number to represent this, the value is what your frame rate would have been in the second if every single frame was as slow as the worst frame that second.  Some other software will show you actual frame times in milliseconds, but we have chosen to convert into FPS to keep the AVG/MIN/MAX in comparable and familiar units.  If you see the ↓Min number turn red, it means we think it's a meaningful drop, which means less than half the average.
 
@@ -26,13 +26,13 @@ It can be hard to look up at the FPS counter in the middle of an important momen
 
 Measuring CPU performance and utilization has also become more complicated as CPUs become more complex over time.  You may be used to some software showing 0-100% CPU utilization numbers that represent the percentage of time the CPU is busy.  On modern many core processors, especially "turbo boost" or "precision boost" types of processors, this simple metric has become much less useful.  Most games can't utilize all cores fully on many core processors, and some cores may run at higher speeds than others.  Windows Task Manager moved to a metric Microsoft calls "% Processor Utility" back in Windows 8, and this is the same metric we use for our CPU % values.  Processor Utility aims to measure the amount of work the CPU is doing scaled to it's base clock rate.  This is useful because a processor running at 50% speed that is busy 100% of the time is doing much less work than a boosted processor running at 120% of base speed running 100% of the time.  Processor Utility numbers allow that difference to be represented.
 
-As a result of using the Processor Utility numbers when your CPU boosts above base clock speed you can see values over 100%.  The utilization numbers we show look like CPU 25%/↑119%.  The first number is the average processor utility across all your cores, we sample this value from Windows once a second.  Many times this number will be low simply because you have many cores and the game is only using some of them due to it's architecture.  The second number is the processor utility value from the OS for the single core that is most utilized at the time we sampled, this number will commonly be over 100% if you have a processor that boosts above it's base clock speed.
+As a result of using the Processor Utility numbers when your CPU boosts above base clock speed you can see values over 100%.  The utilization numbers we show look like CPU 25%/↑119%.  The first number is the average processor utility across all your cores, we sample this value from Windows once a second.  Many times this number will be low simply because you have many cores and the game is only using some of them due to it's architecture.  The second number is the processor utility value from the OS for the single core that is most utilized at the time we sampled, this number will commonly be over 100% if you have a processor that boosts above it's base clock speed.  After this set of numbers, you can optionally enable a bar graph that shows per-core CPU utilization.  The graph can be helpful to visualize how fully a game is utilizing all of your cores on a many core system.
 
 The second set of CPU numbers show you exactly how much your processor might be boosting and are speed numbers commonly shown in Ghz.  The first number is again the average across all cores, and the ↑Max is the highest core at our every 1 second sampling time.
 
 [h2]GPU Performance Info[/h2]
 
-Modern systems may have multiple GPUs, and GPUs have multiple engines (3D, Copy, Video Encode/Decode, etc).  GPUs are core to many games performance and are a common bottleneck on your overall game speed.  The single GPU 95% percent utilization number we choose to show is found by, iterating GPUs and GPU engines, and finding the most used engine.  This will normally be the 3D engine on your primary GPU when in game.  This logic matches Windows Task Manager and should be consistent with it.
+Modern systems may have multiple GPUs, and GPUs have multiple engines (3D, Copy, Video Encode/Decode, etc).  GPUs are core to many games performance and are a common bottleneck on your overall game speed.  The single GPU 82% percent utilization number we choose to show is found by, iterating GPUs and GPU engines, and finding the most used engine.  This will normally be the 3D engine on your primary GPU when in game.  This logic matches Windows Task Manager and should be consistent with it.
 
 After utilization, you may see GPU temperature if you are on a supported vendors card that we are able to pull temperature from.  This is the temperature of the hottest sensor we could query on your GPU.