Skip to content
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.

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

Add test profile for FFXIV Endwalker Benchmark #248

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kotarou3
Copy link

Related feature request: https://www.phoronix.com/forums/forum/phoronix/phoronix-test-suite/1335849-creating-a-test-profile-for-final-fantasy-xiv-endwalker-benchmark

I'm still doing a final bit of testing on whether this needs the "skip first run" option or not, so don't merge this PR just yet.
I'm sending out this PR early so I can get feedback on any changes if needed.

There are also other "editions" of the benchmark available that I might add in the future. But I'm not sure if they should be added as different versions or completely different profiles:

This test calculates the score from the FFXIV Endwalker Benchmark, released in 2021.

Technically a Windows-only benchmark, but also runs at near-native performance under Linux with wine+dxvk (e.g., with the USE_WINE config)</Description>
<ResultScale>Score</ResultScale>
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The benchmark outputs two results: A score, and an average FPS value.
I'm not sure which one is more appropriate here.

The benchmark considers the score the "main" result, but I personally think the average FPS is a more practical result

<ResultsParser>
<ResultScale>Frames Per Second</ResultScale>
<ResultProportion>HIB</ResultProportion>
<OutputTemplate>SCORE_FPSAVERAGE=#_RESULT_#</OutputTemplate>
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The benchmark also produces a list of per-second FPS values looking like this:

KEYS_COUNT=373
K0=33
K1=31
K2=31
...
K370=71
K371=72
K372=72

Is there any way for PTS to capture this info as well? (e.g., for min or 5th percentile FPS)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant