# Can the output of --track-allocation be trusted with multi-threading enabled?

**URL:** <https://discourse.julialang.org/t/can-the-output-of-track-allocation-be-trusted-with-multi-threading-enabled/78744>\
**Category:** Performance\
**Tags:** profiling, allocations\
**Created:** [March 30, 2022, 2:19pm UTC](https://discourse.julialang.org/t/can-the-output-of-track-allocation-be-trusted-with-multi-threading-enabled/78744 "2022-03-30T14:19:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![goerch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerch/32/29122_2.png) [@goerch](https://discourse.julialang.org/u/goerch)\
**Post date:** [March 30, 2022, 3:30pm UTC](https://discourse.julialang.org/t/can-the-output-of-track-allocation-be-trusted-with-multi-threading-enabled/78744/6 "2022-03-30T15:30:44Z")

</div>

Thanks for checking. Sorry I was unclear, I asked because we recently saw [this unrelated problem](https://discourse.julialang.org/t/julia-3-times-slower-than-fortran-reading-integer-data-from-ascii-file/78516/15) in 1.7.2.

Other ideas:

- you could double check with a profiler and search for irregularities
- depending on your program structure you could try `Polyester.jl`’s `@batch` (if this works and behaves differently, please let us now: AFAIK that would be a indicator for the mentioned problem)

---

_[View the full topic](https://discourse.julialang.org/t/can-the-output-of-track-allocation-be-trusted-with-multi-threading-enabled/78744)._