# Debugging extremely slow

**URL:** https://discourse.julialang.org/t/debugging-extremely-slow/53801
**Category:** Tooling
**Tags:** question
**Created:** [January 22, 2021, 7:18pm UTC](https://discourse.julialang.org/t/debugging-extremely-slow/53801 "2021-01-22T19:18:00Z")
**Posts on this page:** 1
**Showing post:** 38

<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: [June 5, 2023, 2:01pm UTC](https://discourse.julialang.org/t/debugging-extremely-slow/53801/38 "2023-06-05T14:01:28Z")

</div>

`push!(JuliaInterpreter.compiled_modules, Base)`. Do this before you start debugging. You can add packages to this, too: `push!(JuliaInterpreter.compiled_modules, SomePackage)`. If you want to be more comprehensive and include inner modules, you can do this:

```julia
using JuliaInterpeter, MethodAnalysis
union!(JuliaInterpreter.compiled_modules, child_modules(Base))

```

This adds an additional 44 modules that are inside `Base`, so that all of Julia’s own code will be run in compiled mode. This should give you an experience that’s a little closer to what you’d get in Matlab or Python, where the internal code is mostly in C and can’t be interpreted.

---

_[View the full topic](https://discourse.julialang.org/t/debugging-extremely-slow/53801)._