Pulsario / Documentation

Troubleshooting

Start with the source, the capabilities, and the clock.

The package cannot be installed

The public PyPI release is upcoming. The proposed pip command is not currently an available public installation method. Existing authorized builds are separate from public publication.

Nsight report fails to open

Check that NVIDIA Nsight Systems is installed locally and nsys is available to the application. Alternatively, open a pre-exported Nsight .sqlite file. Raw .nsys-rep files require the export step.

Symbols are missing

Supply target ELF files that match the recording’s build IDs using --symbols. For kernel symbols, use a kallsyms file from the same boot. Pulsario does not implement perf’s ARM64 leaf-frame caller fixup.

Scheduler information is unavailable

Review the capability report. The source may not contain scheduler data; sched:* payload decoding is also not implemented yet. Do not use CPU sample gaps to infer sleeping, blocked time, or runqueue latency.

pulsario --check perf.data
TERMINAL

The browser did not open

Run the application with --no-browser and a chosen free port, then visit the local address in a browser. Keep the default loopback host for local use.

pulsario --no-browser --port 8080 # Open http://127.0.0.1:8080 in your browser
TERMINAL

File handling and clocks

Browser drag and drop copies files into the application’s local cache. CLI paths and Open by path read files in place. For timing mismatches between sources, review the clock verdict before attempting manual alignment.

UP NEXTFrequently asked questions