tt-enable-tracing

Enable TTNN trace capture and replay to eliminate host dispatch overhead.

341|51|Updated Aug 22, 2024
One-click install
npx skills add https://github.com/tenstorrent/tt-forge --skill tt-enable-tracing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tt-enable-tracing
Source: https://github.com/tenstorrent/tt-forge/tree/main/skills/tt-enable-tracing
Command: npx skills add https://github.com/tenstorrent/tt-forge --skill tt-enable-tracing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TTNN trace capture and replay to eliminate dispatch overhead in TTNN workflows, enabling real-time inference and multi-chip performance.

Core Features & Use Cases

  • Trace capture and replay to remove host dispatch overhead for TTNN ops.
  • Supports multi-chip traces, metal trace APIs, and integration with multiple command queues.
  • Use case: Real-time inference with low latency on TTNN-based systems, streaming workloads.

Quick Start

Capture a trace around your TTNN operations using trace APIs, then replay it with execute_trace to eliminate host dispatch overhead.

Frequently Asked Questions about tt-enable-tracing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce host dispatch overhead during TTNN inference?

To reduce host dispatch overhead during TTNN inference, capture and replay deterministic traces using begin_trace_capture and end_trace_capture APIs to eliminate host bottlenecks.

What is the best way to configure TTNN trace for multi-chip deployments?

Configuring TTNN trace for multi-chip deployments requires setting trace_region_size during device open and preallocating a fixed input tensor to ensure deterministic replay across multiple command queues.

How does trace capture and replay work in TTNN?

TTNN trace capture and replay works by recording operations into a deterministic trace using begin_trace_capture, then executing execute_trace to replay them without host dispatch overhead.

Does TTNN trace support real-time streaming workloads?

Yes, TTNN trace supports real-time streaming workloads by eliminating dispatch overhead, enabling low latency inference and multi-chip performance through metal trace APIs and multiple command queues.

Why do I need to preallocate a fixed input tensor for TTNN trace replay?

Preallocating a fixed input tensor is required for TTNN trace replay to ensure deterministic execution, preventing shape mismatches and maintaining consistent memory addresses during the trace capture and replay process.