MODULE 03 · LESSON 05

Profiling and debugging

Profiling records where runtime time went. Debugging links a symptom to that evidence.

PLAIN-LANGUAGE INTRODUCTION

What is this?

Profiling records where runtime time went. Debugging links a symptom to that evidence.

One simple example

An illustrative trace shows MatMul=12 ms, Add=1 ms, Custom=80 ms, and Copy=7 ms.

A representative model run with profiling and useful logging enabled.

Timed events, provider placement, shapes, and warnings.

Recorded evidence points toward the operation worth investigating first.

One illustrative trace is not a production benchmark.

WORK THROUGH THE IDEA

First define the symptom. Here, one illustrative run totals 100 ms.
The trace assigns 12 ms to MatMul, 1 ms to Add, 80 ms to Custom, and 7 ms to Copy.
The custom operation uses 80% of this made-up total. Inspect its provider and input shape first.
Repeat warm runs under controlled conditions before making a performance claim.
Common mistake: optimizing the largest-looking graph node without checking its recorded duration.