# Gcc vs Threads.@threads vs Threads.@spawn for large loops

**URL:** <https://discourse.julialang.org/t/gcc-vs-threads-threads-vs-threads-spawn-for-large-loops/34273>\
**Category:** Julia at Scale\
**Created:** [February 6, 2020, 8:42pm UTC](https://discourse.julialang.org/t/gcc-vs-threads-threads-vs-threads-spawn-for-large-loops/34273 "2020-02-06T20:42:40Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![j-fu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j-fu/32/11373_2.png) [@j-fu](https://discourse.julialang.org/u/j-fu)\
**Post date:** [February 7, 2020, 11:08am UTC](https://discourse.julialang.org/t/gcc-vs-threads-threads-vs-threads-spawn-for-large-loops/34273/6 "2020-02-07T11:08:51Z")

</div>

Hi, thanks for the hints.

I am trying out ThreadPools, but need to understand more about this package before I would say anything.

`@avx` doesn’t give any additional performance here as it is memory acces bound, but surprisingly it changes the picture with caching and SharedArrays,  
see [my other post](https://discourse.julialang.org/t/are-sharedarrays-bypassing-cache/34269) which I will update.

---

_[View the full topic](https://discourse.julialang.org/t/gcc-vs-threads-threads-vs-threads-spawn-for-large-loops/34273)._