opp-repl-profiling

Profile OMNeT++ simulations with perf and visualize hotspots in Hotspot.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tabgab/opp_repl-skill --skill opp-repl-profiling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opp-repl-profiling
Source: https://github.com/tabgab/opp_repl-skill/tree/main/opp-repl-profiling
Command: npx skills add https://github.com/tabgab/opp_repl-skill --skill opp-repl-profiling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Profile simulations to diagnose performance bottlenecks and verify optimizations in opp_repl projects.

Core Features & Use Cases

  • Linux perf profiling to record call graphs for OMNeT++ simulations.
  • Hotspot visualization to locate and understand hot paths across the simulation.
  • Profile-mode builds to generate suitable binaries and perf data for analysis.
  • Use Case: Diagnosing why a simulation runs slow or validating targeted performance improvements.

Quick Start

Run perf record -g --call-graph dwarf on your opp_repl simulation and open the generated perf.data in Hotspot for analysis.

Frequently Asked Questions about opp-repl-profiling

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

FAQPage Schema
How do I profile OMNeT++ simulation performance bottlenecks on Linux?

Use Linux perf to record call graphs with dwarf debug info and Hotspot to visualize hotspots, diagnosing slow OMNeT++ simulations and verifying performance optimizations.

What build requirements are needed for perf profiling of OMNeT++ simulations?

Profiling OMNeT++ simulations requires a DWARF-enabled profile-mode build, perf tooling access, and Hotspot installed on PATH to generate suitable binaries and perf data.

How does Hotspot visualize perf data from OMNeT++ simulations?

Hotspot visualizes OMNeT++ perf data by loading the recorded perf.data file, displaying hotspots across the simulation workflow to help locate and understand hot paths.

When should I use perf and Hotspot to diagnose slow OMNeT++ simulations?

Use perf and Hotspot to diagnose slow OMNeT++ simulations when you need to identify call graph hotspots, pinpoint performance bottlenecks, or validate targeted optimization improvements.

Can I use perf profiling to verify OMNeT++ simulation optimizations?

Yes, perf profiling verifies OMNeT++ simulation optimizations by recording call graphs and comparing hotspots before and after changes to confirm performance improvements.