# Julia programs now shown on benchmarks game website

**URL:** <https://discourse.julialang.org/t/julia-programs-now-shown-on-benchmarks-game-website/17722>\
**Category:** Community\
**Tags:** announcement\
**Created:** [November 19, 2018, 5:44pm UTC](https://discourse.julialang.org/t/julia-programs-now-shown-on-benchmarks-game-website/17722 "2018-11-19T17:44:02Z")\
**Posts on this page:** 1\
**Showing post:** 145

<div class="post-metadata">

**Author:** ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)\
**Post date:** [December 3, 2019, 3:11pm UTC](https://discourse.julialang.org/t/julia-programs-now-shown-on-benchmarks-game-website/17722/145 "2019-12-03T15:11:05Z")

</div>

This is to be expected in languages, that offer AOT compilation, but don’t have a JIT… It means, they’ll need to deoptimize and basically interpret code in the binary (since they need to execute code, that they haven’t fully inferred ahead of time). Such a JIT-less AOT compilation could also be implemented for Julia 😉 But currently, we only have AOT compilation, that will still JIT compile at runtime, if it runs into code that couldn’t be fully inferred/AOT compiled! That’s also the reason, why most Julia AOT binaries still have compilation overhead, but no actual runtime overhead.

---

_[View the full topic](https://discourse.julialang.org/t/julia-programs-now-shown-on-benchmarks-game-website/17722)._