In the context of gaming and graphics, FPS (frames per second) is commonly used to measure the performance of a system. However, FPS alone doesn't always tell the full story. Another important metric is frame time, which is the time it takes to render each individual frame. Frame time is more directly related to system performance and can give you a clearer understanding of smoothness and consistency.
Frame Time vs FPS
Frame rate (FPS) is the reciprocal of frame time. This means:
- Frame rate (FPS) = 1 / frame time
As frame time approaches 0, the frame rate tends toward infinity, which theoretically means an infinite number of frames can be rendered in a second. However, in practical terms, this is not achievable, and the law of diminishing returns kicks in. At higher FPS levels, improvements in smoothness become less noticeable.
Common FPS Values and Their Corresponding Frame Times
Below is a table that shows common FPS values and their corresponding frame times. As you can see, frame time decreases as FPS increases.
| FPS | Frame Time (ms) |
|---|---|
| 30 FPS | 33.33 ms |
| 60 FPS | 16.67 ms |
| 120 FPS | 8.33 ms |
| 144 FPS | 6.94 ms |
| 240 FPS | 4.17 ms |
| 300 FPS | 3.33 ms |
| 1000 FPS | 1.00 ms |
As shown in the table, increasing the FPS decreases the frame time, which results in faster rendering of each frame. However, the improvements become less noticeable as FPS increases, especially beyond 60-120 FPS. For instance, going from 30 FPS to 60 FPS offers a clear improvement in smoothness, but going from 240 FPS to 300 FPS offers very little perceived difference, even though the frame time has decreased further.
Conclusion
While FPS is a useful metric, frame time is often a better indicator of how well a system is performing, especially in terms of consistency and smoothness. Frame time is linearly related to FPS, and understanding this relationship allows developers and users to focus on more meaningful performance metrics for an improved experience.