uvs-playmode-results-report

스타1

포크0

업데이트2026년 5월 25일 21:55

Reports UVS Benchmark Play Mode performance test results from TestResults XML (Registry, enhanced, or stable). Use when the user asks for a benchmark report, test results summary, performance numbers, or after running uvs-playmode-tests skills.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

miramocha

miramocha/uvs-benchmark

GitHub 저장소 열기 Creator 저장소 보기

다운로드

UVS Play Mode results — report

Summarizes one CLI test run from TestResults/playmode-<source>-*.xml.

Prerequisites

A completed run from Run-UvsPlayModeBenchmarks.ps1 or skills uvs-playmode-tests-registry / uvs-playmode-tests-enhanced.

Report latest run by source

# After Registry 1.9.11 run
.\tools\Report-UvsPlayModeResults.ps1 -Source Registry

# After enhanced run
.\tools\Report-UvsPlayModeResults.ps1 -Source EnhancedGit

Report a specific XML file

.\tools\Report-UvsPlayModeResults.ps1 -ResultsXml "TestResults\playmode-Registry-20260525-120000.xml"

Output

Markdown printed to the terminal
Saved to TestResults/report-<source>-<timestamp>.md

Sections:

Run metadata (file, UVS version/source from sample groups)
All tests table (median/avg/min/max ms)
UVS vs C# ratio table per workload and N

Present results to the user

Run the script (do not guess numbers).
Paste or summarize the generated markdown.
Call out UvsCounter and UvsOverhead at 1000 and 5000 as primary signals.
Note Result column if any test failed.

Parser notes

Metrics are parsed from Unity Performance Testing output in NUnit XML (Median, Avg, etc.). Sample groups look like UvsCounter_1000_registry_1.9.11.

If parsing fails, open the XML output for a UvsCounter_* test and fix regex in tools/UvsPlayModeResults.Parser.ps1.

Next step

For 1.9.11 vs enhanced, use skill uvs-playmode-results-compare after both runs exist.

See docs/benchmarking.md.

이 저장소의 다른 Skills

같은 저장소

uvs-playmode-results-compare

miramocha/uvs-benchmark

Compares UVS Benchmark Play Mode results between Registry 1.9.11 and enhanced (or two XML files). Use when the user asks to compare benchmark runs, delta, enhanced vs stock UVS, or interpret A vs C matrix results.

2026-05-261

uvs-playmode-tests-enhanced

miramocha/uvs-benchmark

Runs UVS Benchmark Play Mode performance tests against the community Visual Scripting fork on the enhanced branch (Git UPM from uvs-benchmark monorepo). Use when the user asks to run benchmark tests on enhanced, Run C, the fork, or community UVS optimizations.

2026-05-261

uvs-playmode-tests-registry

miramocha/uvs-benchmark

Runs UVS Benchmark Play Mode performance tests against Unity Registry Visual Scripting 1.9.11 in uvs-benchmark. Use when the user asks to run benchmark tests on stock 1.9.11, Registry baseline, Run A, or compare against enhanced without naming the enhanced branch.

2026-05-261

name	uvs-playmode-results-report
description	Reports UVS Benchmark Play Mode performance test results from TestResults XML (Registry, enhanced, or stable). Use when the user asks for a benchmark report, test results summary, performance numbers, or after running uvs-playmode-tests skills.
disable-model-invocation	true

UVS Play Mode results — report

Summarizes one CLI test run from TestResults/playmode-<source>-*.xml.

Prerequisites

A completed run from Run-UvsPlayModeBenchmarks.ps1 or skills uvs-playmode-tests-registry / uvs-playmode-tests-enhanced.

Report latest run by source

# After Registry 1.9.11 run
.\tools\Report-UvsPlayModeResults.ps1 -Source Registry

# After enhanced run
.\tools\Report-UvsPlayModeResults.ps1 -Source EnhancedGit

Report a specific XML file

.\tools\Report-UvsPlayModeResults.ps1 -ResultsXml "TestResults\playmode-Registry-20260525-120000.xml"

Output

Markdown printed to the terminal
Saved to TestResults/report-<source>-<timestamp>.md

Sections:

Run metadata (file, UVS version/source from sample groups)
All tests table (median/avg/min/max ms)
UVS vs C# ratio table per workload and N

Present results to the user

Run the script (do not guess numbers).
Paste or summarize the generated markdown.
Call out UvsCounter and UvsOverhead at 1000 and 5000 as primary signals.
Note Result column if any test failed.

Parser notes

Metrics are parsed from Unity Performance Testing output in NUnit XML (Median, Avg, etc.). Sample groups look like UvsCounter_1000_registry_1.9.11.

If parsing fails, open the XML output for a UvsCounter_* test and fix regex in tools/UvsPlayModeResults.Parser.ps1.

Next step

For 1.9.11 vs enhanced, use skill uvs-playmode-results-compare after both runs exist.

See docs/benchmarking.md.