# Overhead of \`Threads.@threads\`

**URL:** https://discourse.julialang.org/t/overhead-of-threads-threads/53964
**Category:** Performance
**Tags:** question, multithreading
**Created:** [January 26, 2021, 10:04am UTC](https://discourse.julialang.org/t/overhead-of-threads-threads/53964 "2021-01-26T10:04:27Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)
#### Post date: [January 27, 2021, 12:07am UTC](https://discourse.julialang.org/t/overhead-of-threads-threads/53964/16 "2021-01-27T00:07:11Z")

</div>

I’m curious about nested schedulers in general. So, I wonder how spin-based task pool management interacts with Julia’s cooperative multitasking. Did you look at scenarios like

```julia
@sync for ...
    @spawn vmap!(...)
end

```

?

Since Julia’s parallel runtime randomizes scheduling, I think an interesting statistics for this is the median (“typical case”) than the minimum (“lucky path”).

---

_[View the full topic](https://discourse.julialang.org/t/overhead-of-threads-threads/53964)._