The first 25 experiments build strong foundations. This follow-up track is designed to convert those foundations into GPU systems and rendering-oriented portfolio evidence.
Bridge objective:
- from isolated benchmark literacy
- to composable GPU subsystem design
- to architecture-aware interpretation suitable for engine and DevTech work
Recommended process:
- use the completed core 25 experiments, plus the extension studies in Experiments 26-33, as the measurement baseline
- identify strongest measured themes (3 to 5)
- choose a focused advanced subset
- execute deeply and compare variants rigorously
Suggested project labeling:
- Project 0.3: focused subset of advanced topics
- Project 0.4: broader multi-topic extension
- Project 1.0: full advanced track with cross-GPU comparisons
Primary themes covered:
- GPU sorting and data reordering
- spatial acceleration structure layout
- visibility and culling pipelines
- persistent work scheduling
- subgroup and wave-level operations
- async compute overlap
- occupancy-guided modeling
- rendering-oriented memory system studies
Detailed lecture-note plans for each investigation live in:
docs/advanced_investigation_plans_index.md, with canonical files beside each experiment asexperiments/<id>/plan.md
Investigation list:
- Radix sort on GPU
- BVH node layout experiments
- Frustum culling vs clustered culling
- Tiled light assignment
- Persistent threads and work queues
- Subgroup operations study
- Async compute overlap
- Occupancy modeling against vendor guidance
- Memory system study for ray-friendly layouts
- Frame-to-frame coherence studies
- GPU-driven pipeline building blocks
- Reproducibility and cross-GPU comparison
- radix sort
- subgroup operations
- occupancy modeling
- tiled light assignment
- frustum vs clustered culling
- GPU-driven building blocks
- BVH layout
- ray-friendly layouts
- frame-to-frame coherence
- persistent work queues
- async overlap
- cross-GPU comparison
Minimum outputs:
- one core chart
- one summary table
- one concise conclusions page with limitations
Recommended folder shape:
experiments/NN_name/
|- README.md
|- plan.md
|- results.md
|- results/
| |- charts/
| `- tables/
`- runs/
- Separate measured facts from interpretation.
- Label inferred occupancy/resource effects as inference, not direct measurement.
- Avoid universal claims from one hardware sample.
- Include failure modes and non-winning variants in conclusions.
Core track message:
- "I understand GPU performance foundations."
Advanced track message:
- "I can apply those foundations to design and analyze practical GPU systems that matter in real rendering and compute pipelines."