사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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.




