# Profiling precompilation (was: \[Plots.jl\] suffers and it’s hard to tell why this is so slow)

**URL:** https://discourse.julialang.org/t/profiling-precompilation-was-plots-jl-suffers-and-it-s-hard-to-tell-why-this-is-so-slow/17360
**Category:** Internals & Design
**Created:** [November 9, 2018, 6:26pm UTC](https://discourse.julialang.org/t/profiling-precompilation-was-plots-jl-suffers-and-it-s-hard-to-tell-why-this-is-so-slow/17360 "2018-11-09T18:26:07Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)
#### Post date: [November 9, 2018, 6:26pm UTC](https://discourse.julialang.org/t/profiling-precompilation-was-plots-jl-suffers-and-it-s-hard-to-tell-why-this-is-so-slow/17360/1 "2018-11-09T18:26:07Z")

</div>

the subject is taken from the [Vizcon , 29th-30th Oct Berlin](https://discourse.julialang.org/t/vizcon-29th-30th-oct-berlin/17326) report about progress in plotting.

But i’m more interested, what tooling is available to see how julia compliation steps spend the time?

---

<div class="post-metadata">

### Author: ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)
#### Post date: [November 9, 2018, 7:08pm UTC](https://discourse.julialang.org/t/profiling-precompilation-was-plots-jl-suffers-and-it-s-hard-to-tell-why-this-is-so-slow/17360/2 "2018-11-09T19:08:02Z")

</div>

You can use `@profile` with `Profile.print(C=true)` to also see the parts that occur in the runtime (ref [use @nospecialize to help with compile time by KristofferC · Pull Request #76 · carlobaldassi/ArgParse.jl · GitHub](https://github.com/carlobaldassi/ArgParse.jl/pull/76)).