# Extremely high first call latency Julia 1.6 versus 1.5 with multiphysics PDE solver

**URL:** <https://discourse.julialang.org/t/extremely-high-first-call-latency-julia-1-6-versus-1-5-with-multiphysics-pde-solver/71692>\
**Category:** Performance\
**Tags:** question\
**Created:** [November 17, 2021, 11:33pm UTC](https://discourse.julialang.org/t/extremely-high-first-call-latency-julia-1-6-versus-1-5-with-multiphysics-pde-solver/71692 "2021-11-17T23:33:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![stillyslalom](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stillyslalom/32/45687_2.png) [@stillyslalom](https://discourse.julialang.org/u/stillyslalom)\
**Post date:** [November 18, 2021, 12:33am UTC](https://discourse.julialang.org/t/extremely-high-first-call-latency-julia-1-6-versus-1-5-with-multiphysics-pde-solver/71692/4 "2021-11-18T00:33:13Z")

</div>

I tried to run your MWE and was stymied by the non-minimal [requirements](https://github.com/gridap/GridapPardiso.jl#requirements) of GridapPardiso.jl. As a longer-term fix, you may want to instead target [Pardiso.jl](https://github.com/JuliaSparse/Pardiso.jl), which should automatically grab BinaryBuilder.jl-provided MKL binaries.

Depending on how your cluster’s filesystem is set up, you may be running into [this issue](https://discourse.julialang.org/t/why-does-julia-use-thousands-of-cpu-hours-to-compute-1-2/66041).

edit: [pending fix](https://github.com/JuliaLang/julia/pull/42156) targeted for Julia 1.8.

---

_[View the full topic](https://discourse.julialang.org/t/extremely-high-first-call-latency-julia-1-6-versus-1-5-with-multiphysics-pde-solver/71692)._