# How to cut down compile time when inference is not the problem?

**URL:** <https://discourse.julialang.org/t/how-to-cut-down-compile-time-when-inference-is-not-the-problem/59077>\
**Category:** Performance\
**Created:** [April 12, 2021, 8:18am UTC](https://discourse.julialang.org/t/how-to-cut-down-compile-time-when-inference-is-not-the-problem/59077 "2021-04-12T08:18:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ranocha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ranocha/32/35588_2.png) [@ranocha](https://discourse.julialang.org/u/ranocha)\
**Post date:** [April 12, 2021, 8:22am UTC](https://discourse.julialang.org/t/how-to-cut-down-compile-time-when-inference-is-not-the-problem/59077/2 "2021-04-12T08:22:28Z")

</div>

Good question and I would also like to see any hints to improvements (although that’s probably a really hard problem). We experienced something similar in our hyperbolic PDE solver framework [Trixi.jl](https://github.com/trixi-framework/Trixi.jl), cf. [this Discourse thread](https://discourse.julialang.org/t/julia-v1-6-using-is-faster-but-first-call-is-slower/54838).

---

_[View the full topic](https://discourse.julialang.org/t/how-to-cut-down-compile-time-when-inference-is-not-the-problem/59077)._