Editor FPS

About This Tool

Editor FPS provides precise FPS estimates to help developers quantify real-time rendering performance across scenes and configurations. It is designed for game engine teams, graphics programmers, and performance QA that need repeatable, auditable metrics. The tool accepts timing data from experiments or logs and outputs standardized results that can be compared over time. Outputs are suitable for automation, dashboards, and integration into build pipelines.
Conceptually the tool consumes timing data in a structured form: total frames counted and the corresponding elapsed time in seconds; optional scene identifiers and sampling windows to segment measurements. It computes FPS as frames divided by time, frame time as time divided by frames multiplied by 1000 to yield milliseconds, and basic statistics such as min, max, average, and percentiles when multiple samples are provided. For per-scene inputs, metrics are aggregated by scene with a clear breakdown. The design prioritizes deterministic behavior and consistent unit handling.
Audience and value: development teams seeking to optimize the rendering pipeline, build engineers validating changes, and stakeholders who need objective performance data. Unique differentiators include per-scene breakdowns, flexible sampling windows, and straightforward export options that integrate with CI/CD, issue trackers, and performance dashboards. It supports automation by providing outputs that are readily consumable by scripts and data pipelines.
Examples: a developer compares FPS between two scene configurations by supplying frames and time for each, then reviews FPS, average frame time, and 95th percentile times. Another use case is tracking FPS across hardware revisions, ensuring measurable improvements. Limitations: measurements rely on input timing data; it does not profile background OS tasks or GPU-level timings unless such inputs are supplied.

Sign in to see all your usage