# Why is LoopVectorization deprecated?

**URL:** <https://discourse.julialang.org/t/why-is-loopvectorization-deprecated/109547>\
**Category:** Performance\
**Tags:** loopvectorization\
**Created:** [February 1, 2024, 2:13am UTC](https://discourse.julialang.org/t/why-is-loopvectorization-deprecated/109547 "2024-02-01T02:13:46Z")\
**Posts on this page:** 1\
**Showing post:** 74

<div class="post-metadata">

**Author:** ![Elrod](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/elrod/32/22461_2.png) [@Elrod](https://discourse.julialang.org/u/Elrod)\
**Post date:** [March 14, 2024, 1:06am UTC](https://discourse.julialang.org/t/why-is-loopvectorization-deprecated/109547/74 "2024-03-14T01:06:13Z")

</div>

Polyester.jl doesn’t depend on LoopVectorization.jl or VectorizationBase.jl, but I think one of the same problems Julia 1.11 introduces impacts it as well, so we shall see.  
Octavian.jl depends heavily on LV, so it is dead without it.  
Tullio.jl will still work and be multithreaded, but performance will suffer for a lot CPU code using it without LV.

---

_[View the full topic](https://discourse.julialang.org/t/why-is-loopvectorization-deprecated/109547)._