# Profiling code reveals that most time is used calling 3 functions in task.jl

**URL:** <https://discourse.julialang.org/t/profiling-code-reveals-that-most-time-is-used-calling-3-functions-in-task-jl/30751>\
**Category:** General Usage\
**Tags:** question\
**Created:** [November 5, 2019, 3:11pm UTC](https://discourse.julialang.org/t/profiling-code-reveals-that-most-time-is-used-calling-3-functions-in-task-jl/30751 "2019-11-05T15:11:18Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![n8xm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/n8xm/32/27536_2.png) [@n8xm](https://discourse.julialang.org/u/n8xm)\
**Post date:** [July 26, 2021, 10:19pm UTC](https://discourse.julialang.org/t/profiling-code-reveals-that-most-time-is-used-calling-3-functions-in-task-jl/30751/15 "2021-07-26T22:19:12Z")

</div>

I have had the same experience. I’ve found that setting the number of threads to be 1 is necessary to avoid spurious results in the profiler.

Should this be reported as an issue in Julia’s standard library, specifically Profile.jl? The Juno issue mentioned by @Pbellive ( [https://github.com/JunoLab/Juno.jl/issues/205](https://github.com/JunoLab/Juno.jl/issues/205) ) is now closed, with the comment that in Juno, “we [now] filter profile traces much better.”

Outside of Juno, though, this still appears to be an issue, and it’s not obvious to a newcomer that multiple threads are the culprit.

---

_[View the full topic](https://discourse.julialang.org/t/profiling-code-reveals-that-most-time-is-used-calling-3-functions-in-task-jl/30751)._