# MKL and sparse solvers

**URL:** <https://discourse.julialang.org/t/mkl-and-sparse-solvers/82292>\
**Category:** General Usage\
**Created:** [June 6, 2022, 4:07am UTC](https://discourse.julialang.org/t/mkl-and-sparse-solvers/82292 "2022-06-06T04:07:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [June 6, 2022, 4:07am UTC](https://discourse.julialang.org/t/mkl-and-sparse-solvers/82292/1 "2022-06-06T04:07:59Z")

</div>

What I wonder is: do the sparse matrix routines of CHOMOD and UMFPACK take advantage of MKL  
behind the scenes? Enabling or disabling MKL (`using MKL`) made absolutely no difference when calling `cholesky` and `lu`.

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [June 6, 2022, 2:59pm UTC](https://discourse.julialang.org/t/mkl-and-sparse-solvers/82292/2 "2022-06-06T14:59:21Z")

</div>

Correction: there is a measurable difference in runtimes after all. But a minor one (~20%).  
Measured on Surface Pro 7, running Windows 10.
