# Debugging invalidations

**URL:** <https://discourse.julialang.org/t/debugging-invalidations/92357>\
**Category:** General Usage\
**Tags:** question, performance, ttfp, bokeh\
**Created:** [December 31, 2022, 11:01am UTC](https://discourse.julialang.org/t/debugging-invalidations/92357 "2022-12-31T11:01:43Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [December 31, 2022, 1:47pm UTC](https://discourse.julialang.org/t/debugging-invalidations/92357/5 "2022-12-31T13:47:02Z")

</div>

I also recommend [Julia v1.9.0-beta2 is fast - #17 by tim.holy](https://discourse.julialang.org/t/julia-v1-9-0-beta2-is-fast/92290/17) over this approach. See discussion in [Add a copy-paste invalidations analysis script by ChrisRackauckas · Pull Request #326 · timholy/SnoopCompile.jl · GitHub](https://github.com/timholy/SnoopCompile.jl/pull/326#pullrequestreview-1233323326) if you’re curious about some of the reasons why; most importantly, it allows you to focus on just the invalidations you need to fix to get precompilation working for specific workloads.

---

_[View the full topic](https://discourse.julialang.org/t/debugging-invalidations/92357)._