Profilers, while they are technically still debuggers, are designed to debug a different element and from a completely different perspective. A profiler is a much lower-level debugging system that is looking at performance and what is attributed to the performance as it stands during execution.
Like standard debuggers, these tools can easily give you insights that lead to finding solutions to high-level problems, but will generally help you determine why your application is running at 14 FPS instead of 60.
There is a tool built right into HoloLens that does a great job of letting you see how your application is running. It displays SoC (system-on-chip) power, system power, Frame Rate, GPU, CPU, input/output, network, and memory. On most of the HoloLens projects I work with this, as this is the first test to perform when performance is not great.Let's take a look at System Performance:
This can be accessed from any PC on the same network...