# Timing compile time phase

**URL:** <https://racket.discourse.group/t/timing-compile-time-phase/3991>\
**Category:** Questions & Answers\
**Created:** [October 28, 2025, 7:34pm UTC](https://racket.discourse.group/t/timing-compile-time-phase/3991 "2025-10-28T19:34:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sora22](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/sora22/32/2622_2.png) [@sora22](https://racket.discourse.group/u/sora22)\
**Post date:** [October 28, 2025, 7:34pm UTC](https://racket.discourse.group/t/timing-compile-time-phase/3991/1 "2025-10-28T19:34:40Z")

</div>

Is there anyone aware of a way to benchmark compile time phases? I haven’t found any in my searches online

---

<div class="post-metadata">

**Author:** ![samth](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/samth/32/3_2.png) [@samth](https://racket.discourse.group/u/samth)\
**Post date:** [October 29, 2025, 1:54pm UTC](https://racket.discourse.group/t/timing-compile-time-phase/3991/2 "2025-10-29T13:54:53Z")

</div>

It depends what you mean, but just using the profiler is what I normally do for understanding the performance of macro expansion. You might also want the environment variables described here: [18.7&nbsp;Controlling and Inspecting Compilation](https://docs.racket-lang.org/reference/compiler.html#%28idx._%28gentag._622._%28lib._scribblings%2Freference%2Freference..scrbl%29%29%29) (see `PLT_EXPANDER_TIMES`).