Live data from Hacker News

Claude Code daily benchmarks for degradation tracking

marginlab.ai

191–200 of 372 posts

Re: Claude Code daily benchmarks for degradation tracking

#192
post #188

Earlier quoted context omitted.

According to Anthropic: "We never reduce model quality due to demand, time of day, or server load." https://www.anthropic.com/engineering/a-postmortem-of-three-...

They've had issues before with things like "TPU top-k error - Claude sometimes dropped the best next token" ( https://www.anthropic.com/engineering/a-postmortem-of-three-... ) so what's going on might not be intentional even.

[deleted]

Re: Claude Code daily benchmarks for degradation tracking

#193
post #74
post #15

Earlier quoted context omitted.

I'm glad I'm not the only one.

One time I cussed Claude out so hard that it actually quit his doom-loop and fixed the thing. It's the only time cussing worked, though.

I don’t know. My gut feeling is it seems to help.

Re: Claude Code daily benchmarks for degradation tracking

#194

Earlier quoted context omitted.

Benchmarks can get costly to run- you can reach out to frontier model creators to try and get them to give you free credits, but usually they'll only agree to that once your benchmark is pretty popular.

so basically they know requests using your API key should be treated with care?

they could but you can also have some trust in anthropic to have some integrity there, these are earnest people.

"trust but verify" ofc . https://latent.space/p/artificialanalysis do api keys but also mystery shopper checks

Re: Claude Code daily benchmarks for degradation tracking

#195
post #57

I am using API mode, and it's clear that there are times when the Claude model just gives up. And it is very noticeable because the model just does the most dumb things possible. "You have a bug in line 23." "Oh yes, this solution is bugged, let me delete the whole feature." That one-line fix I could make even with ChatGPT 3.5 can't just happen. Workflows that I use and are very reproducible start to flake and then f…

Robbing Peter to pay Paul. They are probably resource-constrained, and have determined that it's better to supply a worse answer to more people than to supply a good answer to some while refusing others. Especially knowing that most people probably don't need the best answer 100% of the time.

Right. You can launder quantization that way by muddying the waters of discourse about the model.

Re: Claude Code daily benchmarks for degradation tracking

#197

[SWE-bench co-author here] It seems like they run this test on a subset of 50 tasks, and that they only run the test once per day. So a lot of the movement in accuracy could be attributed to that. I would run on 300 tasks and I'd run the test suite 5 or 10 times per day and average that score. Lots of variance in the score can come from random stuff like even Anthropic's servers being overloaded.

Sorry what? "You can't measure my Cloud Service's performance correctly if my servers are overloaded"? "Oh, you just measured me at bad times each day. On only 50 different queries." So, what does that mean? I have to pick specific times during the day for Claude to code better? Does Claude Code have office hours basically?

chill out, ofir does not work for anthropic. he's just saying there's inherent variability in LLMs and you need to at least 30x the samples that OP is doing in order to make any form of statistically significant conclusions.

Re: Claude Code daily benchmarks for degradation tracking

#198
post #40

[SWE-bench co-author here] It seems like they run this test on a subset of 50 tasks, and that they only run the test once per day. So a lot of the movement in accuracy could be attributed to that. I would run on 300 tasks and I'd run the test suite 5 or 10 times per day and average that score. Lots of variance in the score can come from random stuff like even Anthropic's servers being overloaded.

Agreed, this benchmark would be much more useful ran multiple times a day. That could reveal degredation in line with load patterns.

i recall another project here on HN maybe 4-6 months ago that would run tests 4x a day or something. not sure how to find them again

Re: Claude Code daily benchmarks for degradation tracking

#199
post #114

Lack of transparency as regards "thinking power"-consistency is a big gripe of mine with LLM providers. It's even worse with ChatGPT and the like. E.g. I had to learn the hard way that at >45k input tokens ChatGPT 5.2 Thinking Extended bumps its intelligence down so hard that it can't follow basic instructions (or it somehow truncates the input, losing the instructions). It sucks to lose confidence in an otherwise gr…

Sounds like you ran into the Maximum Effective Context Window: https://arxiv.org/abs/2509.21361?context=cs.AI

Interesting article. Not sure it's the same phenomenon. What I experienced was like a day and night difference when you go from 44.5k to 45.5k. Didn't notice any fluctuation to suggest that it's no a hard 45000 limit. I ran many many queries, similar problem space, but the problems varied a lot.

Re: Claude Code daily benchmarks for degradation tracking

#200
post #18

Why is this happening?

I have absolutely no insight knowledge, but I think it's not a bad assumption to have that, it's costly to run the models, when they release a new model they assume that cost and give per user more raw power, when they've captured the new users and wow factor, they start reducing costs by reducing the capacity they provide to users. Rinse and repeat.

That is absolutely scummy.
Post reply on HN