# Significant compile time latency in Flux with a GAN

**URL:** <https://discourse.julialang.org/t/significant-compile-time-latency-in-flux-with-a-gan/68518>\
**Category:** Machine Learning\
**Tags:** compilation, flux\
**Created:** [September 21, 2021, 10:02am UTC](https://discourse.julialang.org/t/significant-compile-time-latency-in-flux-with-a-gan/68518 "2021-09-21T10:02:00Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![ToucheSir](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/touchesir/32/14411_2.png) [@ToucheSir](https://discourse.julialang.org/u/ToucheSir)\
**Post date:** [November 26, 2021, 8:24pm UTC](https://discourse.julialang.org/t/significant-compile-time-latency-in-flux-with-a-gan/68518/17 "2021-11-26T20:24:37Z")

</div>

I wouldn’t expect to see `precompile` show up (did you ensure the package was already precompiled?), but I don’t know enough about compilation to comment. Ideally any tracing would only start capturing from the point when `pullback` is called (i.e. after all packages are imported and the forward pass is warmed up), but again I’m not sure if that’s possible.

The reason I asked about CPU-only perf is because the cross-post in [Extremely high first call latency Julia 1.6 versus 1.5 with multiphysics PDE solver - #25 by Alexander-Barth](https://discourse.julialang.org/t/extremely-high-first-call-latency-julia-1-6-versus-1-5-with-multiphysics-pde-solver/71692/25) might be indicative of [https://github.com/JuliaGPU/GPUCompiler.jl/issues/65](https://github.com/JuliaGPU/GPUCompiler.jl/issues/65) (lots of time spent in LLVM middle end during GPU compilation).

---

_[View the full topic](https://discourse.julialang.org/t/significant-compile-time-latency-in-flux-with-a-gan/68518)._