Skip to content

Commit c9454cf

Browse files
Refactor fusion documentation: update section title from 'Profiling' to 'Profiling' for consistency
1 parent 5639dcc commit c9454cf

File tree

1 file changed

+1
-1
lines changed
  • content/learning-paths/mobile-graphics-and-gaming/android_halide

1 file changed

+1
-1
lines changed

content/learning-paths/mobile-graphics-and-gaming/android_halide/fusion.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -503,7 +503,7 @@ Fusion isn’t always best. You’ll want to materialize an intermediate (comput
503503
* The intermediate is reused by multiple consumers.
504504
* You need a natural stage to apply parallelization or tiling.
505505

506-
### Profiling
506+
## Profiling
507507
The fastest way to check whether fusion helps is to measure it. The demo prints timing and throughput per frame, but Halide also includes a built-in profiler that reports per-stage runtimes. To learn how to enable and interpret the profiler, see the official [Halide profiling tutorial](https://halide-lang.org/tutorials/tutorial_lesson_21_auto_scheduler_generate.html#profiling).
508508

509509
## Summary

0 commit comments

Comments
 (0)