# Tools to Analyze Long Julia Compilation Times

**URL:** https://discourse.julialang.org/t/tools-to-analyze-long-julia-compilation-times/109510
**Category:** New to Julia
**Tags:** question, compilation
**Created:** [January 31, 2024, 12:54pm UTC](https://discourse.julialang.org/t/tools-to-analyze-long-julia-compilation-times/109510 "2024-01-31T12:54:35Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![SteffenPL](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/steffenpl/32/206270_2.png) [@SteffenPL](https://discourse.julialang.org/u/SteffenPL)
#### Post date: [January 31, 2024, 2:51pm UTC](https://discourse.julialang.org/t/tools-to-analyze-long-julia-compilation-times/109510/3 "2024-01-31T14:51:24Z")

</div>

The thread is quite old. A lot has changed since then. Of course, invalidations are still relevant but SnoopCompile.jl got major updates in between.

Just to be sure, the first step should be profiling with `@profview` or similar tools to see the lines of code most time is spend. Even if runtime is fast, it might give an indication.

Once you go into details, then SnoopCompile.jl, JET.jl and Cthulhu.jl are useful. See also [Optimizing your code](https://modernjuliaworkflows.github.io/pages/optimizing/optimizing/) .

---

_[View the full topic](https://discourse.julialang.org/t/tools-to-analyze-long-julia-compilation-times/109510)._