TiGrIS

tigris analyze

Check if an ONNX model fits your target’s memory constraints before compiling.

Usage

tigris analyze MODEL [OPTIONS]

Options

FlagTypeRequiredDescription
MODELpathyesONNX model file (.onnx)
-m, --memsize (multiple)noMemory pools, fast to slow (e.g. -m 256K or -m 256K -m 8M)
-f, --flashsizenoFlash budget for plan fit check (e.g. 4M)
-v, --verboseflagnoShow per-stage breakdown, tiling analysis, and budget sweep tables

Size Syntax

All size arguments accept the following formats (case-insensitive):

FormatExampleBytes
Plain bytes262144262144
Kilobytes256K or 256KB262144
Megabytes4M or 4MB4194304
Fractional2.5M2621440

Output

When run with a memory budget (-m), the analysis produces three panels:

Model Panel

Summary of the loaded model:

  • Operator and tensor counts
  • Peak activation memory (the minimum SRAM needed if the entire model ran in a single stage)
  • Largest tensor shape and size
  • Quantization status (INT8 QDQ or float32)

SRAM Panel

Memory feasibility analysis against the fast-memory budget:

  • Budget and stage count
  • Spill/reload I/O between stages (bytes transferred between fast and slow memory)
  • Tiling breakdown: how many stages need spatial tiling, how many are tileable vs untileable
  • Verdict: PASS (fits, or resolved by tiling) or FAIL (untileable stages remain or slow memory overflow)

Verdicts:

  • ok: all stages fit within the SRAM budget
  • partitioned: temporal partitioning splits the graph into stages, no tiling needed
  • tiled: spatial tiling resolves all oversized stages
  • needs_work: some stages cannot be tiled and exceed the budget

Flash Panel

Plan size estimate and flash fit check:

  • Weight data size
  • Plan overhead (headers, section directory, tensor/op descriptors)
  • Estimated total plan size
  • LZ4-compressed plan size estimate (shown if compression saves >5%)
  • INT8 plan size estimate (shown for float32 models)
  • Flash fit verdict when -f is provided

Examples

Basic feasibility check:

tigris analyze ds_cnn.onnx -m 256K

Check against both SRAM and flash budgets:

tigris analyze mobilenetv2.onnx -m 256K -f 4M

Two-pool memory (SRAM + PSRAM):

tigris analyze yolov5n.onnx -m 232K -m 6M -f 4M

Verbose output with per-stage and tiling tables:

tigris analyze ds_cnn.onnx -m 64K -v

With -v, additional tables are shown:

  • Budget Comparison: how stage counts and tiling requirements change across a range of SRAM budgets
  • Stages: per-stage op count, peak memory, input/output tensor counts, and warnings
  • Tiling Analysis: per-stage tile height, tile count, halo, receptive field, and tiled peak memory
Prev
Core Concepts
Next
tigris compile