# Best practices for profiling compilation

**URL:** <https://discourse.julialang.org/t/best-practices-for-profiling-compilation/48249>\
**Category:** Performance\
**Tags:** compilation\
**Created:** [October 12, 2020, 6:21pm UTC](https://discourse.julialang.org/t/best-practices-for-profiling-compilation/48249 "2020-10-12T18:21:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tim.holy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim.holy/32/52_2.png) [@tim.holy](https://discourse.julialang.org/u/tim.holy)\
**Post date:** [October 13, 2020, 1:40pm UTC](https://discourse.julialang.org/t/best-practices-for-profiling-compilation/48249/2 "2020-10-13T13:40:14Z")

</div>

Didn’t see this before I posted [Understanding precompilation and its limitations (reducing latency)](https://discourse.julialang.org/t/understanding-precompilation-and-its-limitations-reducing-latency/48294), but that addresses some of what you’re asking about.

---

_[View the full topic](https://discourse.julialang.org/t/best-practices-for-profiling-compilation/48249)._
