# Building julia with \`march=native\`

**URL:** <https://discourse.julialang.org/t/building-julia-with-march-native/82256>\
**Category:** General Usage\
**Created:** [June 5, 2022, 2:07am UTC](https://discourse.julialang.org/t/building-julia-with-march-native/82256 "2022-06-05T02:07:21Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [June 5, 2022, 10:55am UTC](https://discourse.julialang.org/t/building-julia-with-march-native/82256/12 "2022-06-05T10:55:25Z")

</div>

> [@sobhan](#):
>
> but overall performance gains seemed to be inconclusive at best.

Keep in mind that julia is a compiler itself: the performance of the code it generates shouldn’t in principle depend much (or at all?) on how it was compiled, by default it compiles natively for the target system in any case. That said, by doing a native build what _could_ improve is performance of the runtime (compilation latency, garbage collector, etc…), but depending on workload you benchmark this can have varying impact, sometimes negligible, other times more significant.

---

_[View the full topic](https://discourse.julialang.org/t/building-julia-with-march-native/82256)._