使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/prag-matt-ic/threenix-plugin --skill threenix-benchmark-webgpu開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Benchmark Three.js WebGPU work
Measure a representative render or compute workload without changing production code. Read the benchmark guide for the runner command, fixture contract, and interpretation limits.
- Inspect the target project, its Three.js version, the real code path, and any existing fixture. Choose fixed inputs that represent the requested workload. The bundled runner needs a hardware WebGPU adapter with timestamp queries and a Node-compatible fixture; browser-only behavior needs a browser measurement instead.
- Build or adapt a fixture around the actual target code. Declare edited source dependencies and fixed workload inputs. Do not substitute the guide's synthetic example for a component measurement. If a faithful fixture cannot run, report the limitation without inventing timings.
- Run the bundled
scripts/benchmark.mjsinto a new output directory. Repeat the unchanged workload to establish timing noise. For an edit comparison, capture the baseline before the edit and use--baselinewith the same fixture and settings afterward. Keep the original artifacts intact. - Inspect GPU timing samples, workload and environment compatibility, shader snapshots, and output bytes. Investigate output differences. Repeat A/B runs under comparable conditions before claiming an improvement.
- Report the fixture, hardware, settings, artifact paths, medians and p05–p95 ranges, output comparison, and uncertainty. Pass timing does not identify the limiting shader stage or predict application FPS. A standalone baseline is a measurement, not a speedup claim.




