Skip to content

[API] Report FPS in a standardized way #604

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ArielG-NV wants to merge 3 commits into from
+102 −555
Closed

[API] Report FPS in a standardized way #604

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
baaabcf
report FPS in a standardized way.
ArielG-NV Sep 9, 2026
7eac488
format
ArielG-NV Sep 9, 2026
d6e4421
ai test breaks, test is not very correct/useful
ArielG-NV Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -356,6 +356,12 @@ The nested `integrations_v2/omnidreams/impl/ludus-renderer` workspace package is
named `ludus-renderer` and is installed as part of Omnidreams workflows
that need it.

## Benchmarking

Trigger benchmarking via the demo argument (before `--`): `--stats-path <path>.json`.

`MetricsOutputSink::close` is currently where the schema of our "standardized" benchmark artifact is defined.

## Licensing of contributions

By submitting a pull request to this repository, you agree that your
Expand Down
Loading
Loading