# Julia faster than C++ on a converted large simulation model

**URL:** <https://discourse.julialang.org/t/julia-faster-than-c-on-a-converted-large-simulation-model/139787>\
**Category:** General Usage\
**Created:** [October 2, 2026, 10:18am UTC](https://discourse.julialang.org/t/julia-faster-than-c-on-a-converted-large-simulation-model/139787 "2026-10-02T10:18:00Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![xlxs4](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xlxs4/32/224566_2.png) [@xlxs4](https://discourse.julialang.org/u/xlxs4)\
**Post date:** [October 2, 2026, 10:10pm UTC](https://discourse.julialang.org/t/julia-faster-than-c-on-a-converted-large-simulation-model/139787/10 "2026-10-02T22:10:02Z")

</div>

If a typical codepath in a 12 year old codebase becomes more than 6 times faster by just changing a map to an unsorted map, and by not repeatedly constructing and tearing down strings inside a hot loop, this is just code that nobody sought to optimize. Especially when it comes to controlling memory layout I’d say a systems language does way better than Julia. The fact that your LLM happened to optimize that part of the code has nothing to do with either language. Extrapolating from all of this to the OP claim is clickbait, IMO.

---

_[View the full topic](https://discourse.julialang.org/t/julia-faster-than-c-on-a-converted-large-simulation-model/139787)._
