# Taking TTFX seriously: Can we make common packages faster to load and use

**URL:** <https://discourse.julialang.org/t/taking-ttfx-seriously-can-we-make-common-packages-faster-to-load-and-use/74949>\
**Category:** Performance\
**Tags:** ttfp\
**Created:** [January 20, 2022, 5:16pm UTC](https://discourse.julialang.org/t/taking-ttfx-seriously-can-we-make-common-packages-faster-to-load-and-use/74949 "2022-01-20T17:16:03Z")\
**Posts on this page:** 1\
**Showing post:** 115

<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:** [February 8, 2022, 8:19am UTC](https://discourse.julialang.org/t/taking-ttfx-seriously-can-we-make-common-packages-faster-to-load-and-use/74949/115 "2022-02-08T08:19:23Z")

</div>

One of the things that’s not been mentioned is to check whether you’re over-specializing. Gains like those in [Understanding and optimizing compiler time (just a bit) - #13 by Tamas\_Papp](https://discourse.julialang.org/t/understanding-and-optimizing-compiler-time-just-a-bit/51759/13) are only possible in rare circumstances, but milder versions are fairly common. The fastest way I know of to gain insights about this is [Profile-guided despecialization · SnoopCompile](https://timholy.github.io/SnoopCompile.jl/stable/pgdsgui/). A lower-tech approach is to use `using MethodAnalysis; methodinstances(MyPkg)` and just browse the list. You have to run workloads first for this to be useful.

The reason I emphasize this point is that reducing needless specialization is likely to be useful long-term, whereas understandable frustrations with things like forced-precompilation not making much difference may be more transitory as Julia itself improves.

---

_[View the full topic](https://discourse.julialang.org/t/taking-ttfx-seriously-can-we-make-common-packages-faster-to-load-and-use/74949)._