filtrace

Rank and drill into hot paths in .NET traces and speedscope exports.

9|1|Updated Jun 6, 2025

Search Tags:#profiling #dotnet #cpu #jit #allocations #trace-analysis #nettrace

Ready to run

npx skills add https://github.com/JeremyKuhne/touki --skill filtrace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: filtrace
Source: https://github.com/JeremyKuhne/touki/tree/main/.agents/skills/filtrace
Command: npx skills add https://github.com/JeremyKuhne/touki --skill filtrace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes .NET traces to help developers quickly identify where time and memory are spent, enabling precise performance investigations and optimization decisions.

Core Features & Use Cases

Rank CPU, allocations, exceptions, and thread-time to surface hotspots across .NET traces (.nettrace, .etl) and speedscope exports.
Drill into hot frames with callers, lines, heatmaps, and call trees to locate exact source lines driving cost.
Compare traces with diff and export flame graphs or structured reports to share findings with teams.
Works via CLI or MCP server and supports both modern .NET and .NET Framework profiling scenarios.

Quick Start

Run filtrace to analyze a captured trace (for example app.nettrace) and identify the top hot frame.

Frequently Asked Questions about filtrace

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

FAQPage Schema

How do I find CPU hot spots in a .NET trace?▼

You can identify hot paths in .NET traces by ranking CPU usage and drilling into hot frames with callers, heatmaps, and call trees to locate exact source lines driving cost across .nettrace and .etl files.

What is the best way to analyze memory allocations in .NET traces?▼

The best way to analyze memory allocations in .NET traces is to rank allocation data to surface hotspots, then drill into call trees to pinpoint exact source lines driving memory cost across .nettrace, .etl, and speedscope formats.

Does .NET trace analysis work with both .NET and .NET Framework profiling scenarios?▼

Yes, .NET trace analysis supports both modern .NET and .NET Framework profiling scenarios, covering CPU, memory, GC, JIT, and thread-time analyses through CLI and MCP server workflows.

Can I compare .NET traces and export flame graphs to share with my team?▼

Yes, you can compare .NET traces using diff and export flame graphs or structured reports to share performance findings and optimization decisions with your team.

How do I drill into JIT and thread-time hotspots in a .nettrace file?▼

You can drill into JIT and thread-time hotspots in a .nettrace file by ranking resource usage metrics and examining hot frames with callers and line numbers to isolate where execution time is spent.