You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PresentMon 2.0.0 shows an FPS value for the Presented FPS metric, but your "X%" percentile refers to (frame)times, not FPS. This way can be a bit misleading or confusing, as with a correct formulation, the 99th percentile of (frame)times [99% of the values are lower] corresponds to the 1st percentile of FPS [99% of the values are higher], and the 1st percentile of (frame)times [1% of the values are lower] corresponds to the 99th percentile of FPS [1% of the values are higher].
Taxxor, one of the CapFrameX developers, covered this topic and explained this issue very well in the following article:
So, here is a suggestion or enhancement for a future PresentMon version:
With a correct formulation, if you show a Presented FPS metric, you may want to display the Xth percentile of FPS, not the Xth percentile of (frame)times, as the unit of the overlayed shown metric is FPS, not (frame)times.
So, your Presented FPS (1%) metric may result in and show the 1st percentile of FPS or P1 FPS (99% of samples are higher than the displayed FPS value, and 1% of samples are less than or equal to such displayed FPS value). Accordingly, your Presented FPS (99%) metric may display the 99th percentile of FPS or P99 FPS (1% of samples are higher than such FPS value, and 99% of samples are lower than or equal to such FPS value).
Please consider this as a future app overlay enhancement. Kind regards.
The text was updated successfully, but these errors were encountered:
RodroG-85
changed the title
Display the Presented FPS metric as the Xth percentile of FPS, not the Xth percentile of (frame)times
Display the Presented FPS (X%) metric as the Xth percentile of FPS, not the Xth percentile of (frame)times
Apr 20, 2024
PresentMon 2.0.0 shows an FPS value for the Presented FPS metric, but your "X%" percentile refers to (frame)times, not FPS. This way can be a bit misleading or confusing, as with a correct formulation, the 99th percentile of (frame)times [99% of the values are lower] corresponds to the 1st percentile of FPS [99% of the values are higher], and the 1st percentile of (frame)times [1% of the values are lower] corresponds to the 99th percentile of FPS [1% of the values are higher].
Taxxor, one of the CapFrameX developers, covered this topic and explained this issue very well in the following article:
Explanation of Different Performance Metrics
So, here is a suggestion or enhancement for a future PresentMon version:
With a correct formulation, if you show a Presented FPS metric, you may want to display the Xth percentile of FPS, not the Xth percentile of (frame)times, as the unit of the overlayed shown metric is FPS, not (frame)times.
So, your Presented FPS (1%) metric may result in and show the 1st percentile of FPS or P1 FPS (99% of samples are higher than the displayed FPS value, and 1% of samples are less than or equal to such displayed FPS value). Accordingly, your Presented FPS (99%) metric may display the 99th percentile of FPS or P99 FPS (1% of samples are higher than such FPS value, and 99% of samples are lower than or equal to such FPS value).
Please consider this as a future app overlay enhancement. Kind regards.
The text was updated successfully, but these errors were encountered: