# Profiling with presets

**URL:** https://discourse.cmake.org/t/profiling-with-presets/15516
**Category:** Usage
**Created:** [February 19, 2026, 11:26am UTC](https://discourse.cmake.org/t/profiling-with-presets/15516 "2026-02-19T11:26:14Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![w124513](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/w/cab0a1/32.png) [@w124513](https://discourse.cmake.org/u/w124513)
#### Post date: [February 19, 2026, 11:26am UTC](https://discourse.cmake.org/t/profiling-with-presets/15516/1 "2026-02-19T11:26:14Z")

</div>

Is there a plan to make profiling available through presets?

---

<div class="post-metadata">

### Author: ![craig.scott](https://discourse.cmake.org/user_avatar/discourse.cmake.org/craig.scott/32/20_2.png) [@craig.scott](https://discourse.cmake.org/u/craig.scott)
#### Post date: [February 19, 2026, 9:32pm UTC](https://discourse.cmake.org/t/profiling-with-presets/15516/2 "2026-02-19T21:32:32Z")

</div>

Assuming you’re referring to profiling the CMake run itself, that doesn’t seem like something appropriate for a preset. It shouldn’t be something you enable except for specific circumstances where you want to investigate something. Enabling profiling has a cost on configure time.

To directly answer your question, I’m not aware of anyone working on adding such support (I don’t plan to).

---

<div class="post-metadata">

### Author: ![w124513](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/w/cab0a1/32.png) [@w124513](https://discourse.cmake.org/u/w124513)
#### Post date: [February 23, 2026, 7:23am UTC](https://discourse.cmake.org/t/profiling-with-presets/15516/3 "2026-02-23T07:23:41Z")

</div>

I would argue that the same thing is true for tracing - which is already part of the preset system.