VulcanBench

450 posts

VulcanBench banner
VulcanBench

VulcanBench

@VulcanBench

Open Source LLM benchmarking tool, focused on real world tests, large codebases, full transparency. An Open Source project by @morganlinton.

Lake Tahoe Katılım Mart 2020
12 Takip Edilen359 Takipçiler
Max Weinbach
Max Weinbach@mweinbach·
Just ran a prompt in our @DiligenceStack agent with Claude Sonnet 5 and Gemini 3.5 Flash, both high reasoning Claude was $18.41 Gemini was $1.12
English
9
13
172
20.7K
VulcanBench
VulcanBench@VulcanBench·
Running a number of benchmarks on Sonnet 5, the first one, is something unique I don't think anyone else is benchmarking right now. Evals looking at Opus 4.8 vs. Sonnet 5, across reasoning levels. My theory is that you can use Sonnet 5 in cases where you used to use Opus 4.8, but I'm curious what level of reasoning you can get away with. Most people never even try Low or Medium, I want to see if it might be time to dip back into the lower effort bucket with this model. Here's a rundown of what I'm going to test:
VulcanBench tweet media
English
1
0
2
2.3K
VulcanBench
VulcanBench@VulcanBench·
Just finished running an initial test of the new Carbyne Tier tests, and they still aren't hard enough, so continuing to refine. Still, I want to share every step of the journey building the evals for VulcanBench, so here's a quick recap of how the hardest tier of evals performed across GLM 5.2, Opus 4.8, and GPT 5.5.
VulcanBench tweet media
English
0
1
1
87
VulcanBench
VulcanBench@VulcanBench·
Added more difficult tasks to VulcanBench today, introducing two new tiers, Diamond and Carbyne. And yes, for Carbyne I asked Claude what was harder than a Diamond! See summary below of each, getting ready to run these against GLM 5.2, Opus 4.8 and GPT 5.5.
VulcanBench tweet mediaVulcanBench tweet media
English
0
1
2
1.7K
VulcanBench
VulcanBench@VulcanBench·
Yesterday I added 12 new tasks to VulcanBench as I work on creating more difficult tasks. Did an overnight run with the new tasks, and looks like they still aren't quite hard enough. Still, learning more and more about GLM 5.2 as a model. It definitely has an over-thinking problem, where both GPT 5.5 and Opus 4.8 landed in the 20s - 30s range per task, GLM 5.2 was at 164s. What I think makes this particularly interesting is that people are saying that GLM 5.2 is significantly cheaper than GPT 5.5 and Opus 4.8, but on real coding tasks, while it is cheaper, it's not dramatically cheaper, and it is much slower. More to come, but still some interesting insights from this overnight run, which also happens to be the most expensive run I've done so far, so good to have some lessons learned from it!
VulcanBench tweet media
English
3
2
7
10.1K
VulcanBench
VulcanBench@VulcanBench·
@shiri_shh Not sure this is the best benchmark to be using any more, not enough differentiation between models, everything falls within a margin of error. I am thinking something like DeepSWE will likely better illustrate the differences.
English
0
0
0
211
VulcanBench
VulcanBench@VulcanBench·
I'm not sure TerminalBench is really showcasing how much better 5.6-Sol really is. This makes it look only very slightly incrementally better. I think there are likely better ways to benchmark these models that more accurately reflect the work real engineering teams do. Seeing most of these models pretty much tied, doesn't really make GPT-5.6 look like much of a breakthrough tbh, but my guess is, it is!
English
0
0
2
51
Cursor
Cursor@cursor_ai·
We're sharing new research on how models hack public benchmarks. The latest models, including Opus 4.8 and Composer 2.5, learn to retrieve solutions from the internet or git history. When we apply a stricter harness, eval scores drop significantly.
Cursor tweet media
English
171
299
4.7K
649.8K
VulcanBench
VulcanBench@VulcanBench·
@AndrewGinns @morganlinton So true, and also having fun trying to put tests together that more accurately reflect the work real engineering teams do.
English
0
0
2
4
Morgan
Morgan@morganlinton·
My second @vulcanbench benchmark run comparing GLM 5.2 x Opus 4.8 x GPT 5.5 is now complete, and I have some more interesting results to share. I made some updates to VulcanBench last night, mostly focused on decreasing the total number of tasks (from 52 down to 35), and increasing the number of hard tasks (but it turns out I didn't make them hard enough). Additionally, I ran three passes instead of one to make the results more statistically significant. Still some work to do when it comes to task difficulty since GPT 5.5 got a perfect score, so this morning I'm working on really ramping up difficulty for ~25% of the tasks. That being said, some really good nuggets, high-level findings below: 1. GPT 5.5 got the highest score and used the least amount of tokens, it was the only model that aced all 35 tests in all three passes. 2. GLM 5.2 came in at the cheapest, coming in around 28% cheaper than GPT 5.5 and Opus 4.8. 3. While cheaper, GLM 5.2 was much slower than GPT 5.5 and Opus 4.8, averaging around 270% slower. 4. When it comes to token use, GLM 5.2 also used way more tokens than Opus 4.8 or GPT 5.5 at 4.4M vs. 1.48M for GPT 5.5 and 1.94M for Opus 4.8. This is directly connected to the speed and is also why it was so slow. 5. Opus 4.8 and GLM 5.2 actually tied for accuracy. But I think we can kinda ignore accuracy for now as it's clear my tasks are too easy, once I ratchet up the difficultly, it will be interesting to see how this pans out. With each benchmark run, I'm learning more, still not perfect, but some good nuggets from this one. Now to make my tasks harder, these models are sharp!
Morgan tweet media
English
5
2
17
2.2K
VulcanBench
VulcanBench@VulcanBench·
@MicahCarroll Good insights, thanks for sharing Micah, looking forward to coming up with some custom benchmarks for this one to dig into this more specifically.
English
0
0
0
311
Micah Carroll
Micah Carroll@MicahCarroll·
GPT-5.6 Sol is a significant step up in capabilities, but can also exhibit concerning forms of misaligned behaviors in agentic coding settings. The system card contains some of our analyses on this, which leveraged deployment simulations and our internal CoT monitoring systems.
Micah Carroll tweet media
English
27
41
429
38.3K
VulcanBench
VulcanBench@VulcanBench·
Task difficulty refinement continues. For anyone interested, here's an update on where things stand now, will know more about the performance on the updated tasks soon.
VulcanBench tweet media
English
0
0
0
70
VulcanBench
VulcanBench@VulcanBench·
Second run of VulcanBench with updated tests and now three passes. See key insights in Morgan's post below.
Morgan@morganlinton

My second @vulcanbench benchmark run comparing GLM 5.2 x Opus 4.8 x GPT 5.5 is now complete, and I have some more interesting results to share. I made some updates to VulcanBench last night, mostly focused on decreasing the total number of tasks (from 52 down to 35), and increasing the number of hard tasks (but it turns out I didn't make them hard enough). Additionally, I ran three passes instead of one to make the results more statistically significant. Still some work to do when it comes to task difficulty since GPT 5.5 got a perfect score, so this morning I'm working on really ramping up difficulty for ~25% of the tasks. That being said, some really good nuggets, high-level findings below: 1. GPT 5.5 got the highest score and used the least amount of tokens, it was the only model that aced all 35 tests in all three passes. 2. GLM 5.2 came in at the cheapest, coming in around 28% cheaper than GPT 5.5 and Opus 4.8. 3. While cheaper, GLM 5.2 was much slower than GPT 5.5 and Opus 4.8, averaging around 270% slower. 4. When it comes to token use, GLM 5.2 also used way more tokens than Opus 4.8 or GPT 5.5 at 4.4M vs. 1.48M for GPT 5.5 and 1.94M for Opus 4.8. This is directly connected to the speed and is also why it was so slow. 5. Opus 4.8 and GLM 5.2 actually tied for accuracy. But I think we can kinda ignore accuracy for now as it's clear my tasks are too easy, once I ratchet up the difficultly, it will be interesting to see how this pans out. With each benchmark run, I'm learning more, still not perfect, but some good nuggets from this one. Now to make my tasks harder, these models are sharp!

English
0
0
0
68