# A new LLM benchmark for Julia programming

**URL:** https://discourse.julialang.org/t/a-new-llm-benchmark-for-julia-programming/129193
**Category:** Tooling
**Tags:** ai
**Created:** [May 21, 2025, 1:38am UTC](https://discourse.julialang.org/t/a-new-llm-benchmark-for-julia-programming/129193 "2025-05-21T01:38:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![arjunguha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/arjunguha/32/214464_2.png) [@arjunguha](https://discourse.julialang.org/u/arjunguha)
#### Post date: [May 21, 2025, 1:38am UTC](https://discourse.julialang.org/t/a-new-llm-benchmark-for-julia-programming/129193/1 "2025-05-21T01:38:50Z")

</div>

I know some people in this community are interested in seeing LLMs get better at Julia. But, you can’t make any progress in machine learning without a good benchmark.

We have started work on a new LLM benchmark that supports Julia. It is very early, but I think it is already much higher quality than prior efforts (including my own prior work on [MultiPL-E](https://github.com/nuprl/MultiPL-E)). Moreover, I think the benchmarking methodology makes it much particularly easy to add new problems. The latter is really important, because writing a good benchmark is painful!

There is more information in the [repository readme](https://github.com/arjunguha/BigCodeBench-MultiPL/), including some preliminary results. If others are interested, I’d be happy to work together. I’m hopeful this will be a useful community resource.

---

<div class="post-metadata">

### Author: ![JohnCobbler](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johncobbler/32/222108_2.png) [@JohnCobbler](https://discourse.julialang.org/u/JohnCobbler)
#### Post date: [June 9, 2026, 12:36pm UTC](https://discourse.julialang.org/t/a-new-llm-benchmark-for-julia-programming/129193/3 "2026-06-09T12:36:04Z")

</div>

On the idioms angle — what started the original fine-tuning thread was the failures general models make that aren’t wrong, just un-Julian. BigCodeBench-MultiPL is pass@1 functional correctness, so a correct-but-un-idiomatic answer scores the same as an idiomatic one. Is idiom-sensitivity something we’d want in scope?  
Separately, I have an RTX 6000 and I’ve been fine-tuning small models (1–8B) — happy to run candidates against this benchmark and report back. And if enough people want it, I’m open to bootstrapping a from-scratch cloud train and releasing the weights OSS. Thus gauging interest now before committing the compute. Preferably something that would fit my local setup in 4-bit quant.

---

<div class="post-metadata">

### Author: ![davide.crucitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davide.crucitti/32/218224_2.png) [@davide.crucitti](https://discourse.julialang.org/u/davide.crucitti)
#### Post date: [June 10, 2026, 12:24pm UTC](https://discourse.julialang.org/t/a-new-llm-benchmark-for-julia-programming/129193/4 "2026-06-10T12:24:26Z")

</div>

I could commit compute towards this. I do not have time to work on the optimization and design of the system, but if you have the system ready to train I can run the training and give you back the results.

---

<div class="post-metadata">

### Author: ![arjunguha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/arjunguha/32/214464_2.png) [@arjunguha](https://discourse.julialang.org/u/arjunguha)
#### Post date: [June 12, 2026, 12:48pm UTC](https://discourse.julialang.org/t/a-new-llm-benchmark-for-julia-programming/129193/5 "2026-06-12T12:48:44Z")

</div>

We’re only starting to see benchmarks that test if code is idiomatic. I think the latest FrontierCode benchmark does that for Python. But it’s definitely interesting to do.
