# Installation on managed cluster

**URL:** <https://discourse.julialang.org/t/installation-on-managed-cluster/100145>\
**Category:** General Usage\
**Tags:** cluster, installation\
**Created:** [June 10, 2023, 5:12pm UTC](https://discourse.julialang.org/t/installation-on-managed-cluster/100145 "2023-06-10T17:12:54Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [July 4, 2023, 8:44am UTC](https://discourse.julialang.org/t/installation-on-managed-cluster/100145/21 "2023-07-04T08:44:40Z")

</div>

Hi all, I just started creating these notes - so they’re obviously WIP - but maybe they are helpful:

[https://juliahpc.github.io/JuliaOnHPCClusters/sysadmin\_julia/](https://juliahpc.github.io/JuliaOnHPCClusters/sysadmin_julia/)

(Feel free to ask questions, file issues, and/or make PRs!)

---

<div class="post-metadata">

**Author:** ![jishnub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jishnub/32/33620_2.png) [@jishnub](https://discourse.julialang.org/u/jishnub)\
**Post date:** [July 4, 2023, 8:59am UTC](https://discourse.julialang.org/t/installation-on-managed-cluster/100145/22 "2023-07-04T08:59:40Z")

</div>

This is great! It would be helpful if you could also provide steps to use a system-provided MKL module, as the current docs are a bit tenuous. I note that you had started [a thread](https://github.com/JuliaLinearAlgebra/MKL.jl/issues/82) on this sometime back, but the steps involved in the resolution aren’t clear.

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [July 4, 2023, 9:44am UTC](https://discourse.julialang.org/t/installation-on-managed-cluster/100145/23 "2023-07-04T09:44:51Z")

</div>

Yeah, I’ve lost interest in this and would need to resurrect the [corresponding PR](https://github.com/JuliaLinearAlgebra/MKL.jl/pull/84).

May I ask why you want to use a system MKL?

For me, the reason was mainly to save disk space (i.e. avoid the redundancy of every user installing MKL\_jll.jl separately) and I changed my view on this: While it would be “nice to have” I couldn’t care less these days about this little disk space on an HPC cluster 🙂  
(Also the fundamental issue is that we don’t have [prevent overridden artifacts from downloading by KristofferC · Pull Request #3076 · JuliaLang/Pkg.jl · GitHub](https://github.com/JuliaLang/Pkg.jl/pull/3076) yet.)

If your motivation isn’t saving disk space than [Add mkl\_provider option to support using "system" MKL by carstenbauer · Pull Request #84 · JuliaLinearAlgebra/MKL.jl · GitHub](https://github.com/JuliaLinearAlgebra/MKL.jl/pull/84) (or even a simplified version of it) is enough.

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [July 4, 2023, 10:57am UTC](https://discourse.julialang.org/t/installation-on-managed-cluster/100145/24 "2023-07-04T10:57:10Z")

</div>

@jishnub I’ve resurrected [the PR](https://github.com/JuliaLinearAlgebra/MKL.jl/pull/84). Should be close to the finish line now (it works fine for me locally).

---

<div class="post-metadata">

**Author:** ![jishnub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jishnub/32/33620_2.png) [@jishnub](https://discourse.julialang.org/u/jishnub)\
**Post date:** [July 4, 2023, 11:06am UTC](https://discourse.julialang.org/t/installation-on-managed-cluster/100145/25 "2023-07-04T11:06:02Z")

</div>

> May I ask why you want to use a system MKL?

I had assumed that the sysadmins would be able to build MKL to play better with AMD EPYC cores, on which the default MKL that’s downloaded seems not to obtain any multi-threading at all. Although, I don’t know whether this is the case one way or the other.

Thank you very much for your effort, in any case

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [July 4, 2023, 8:46pm UTC](https://discourse.julialang.org/t/installation-on-managed-cluster/100145/26 "2023-07-04T20:46:45Z")

</div>

> [@jishnub](#):
>
> I had assumed that the sysadmins would be able to build MKL to play better with AMD EPYC cores

You don’t “build MKL” since there is no source code to build to start with. The AMD trick consists of preloading a library which implements a single function which turns on not-too-bad kernels for AMD CPUs, but that works also with JLLs and it’s tangential to what’s the provider of your MKL

[Previous page](https://discourse.julialang.org/t/installation-on-managed-cluster/100145.md?page=1)