Live data from Hacker News

Claude Code daily benchmarks for degradation tracking

marginlab.ai

71–80 of 372 posts

Re: Claude Code daily benchmarks for degradation tracking

#71

My personal conspiracy theory is that they choose who to serve a degraded model to based on social graph analysis and sentiment analysis, maximizing for persuasion while minimizing compute.

Sounds more like a sound business plan than a conspiracy theory.

Re: Claude Code daily benchmarks for degradation tracking

#72

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.

The last thing a proper benchmark should do is reveal it's own API key.

That's a good thought I hadn't had, actually.

Re: Claude Code daily benchmarks for degradation tracking

#73

Wouldn't be surprised if they slowly start quantizing their models over time. Makes it easier to scale and reduce operational cost. Also makes a new release have more impact as it will be more notably "better" than what you've been using the past couple of days/weeks.

It sure feels like they do this. They claim they don't, but using it every day for 5-10 hours a day. You notice when something changes.

This last week it seems way dumber than before.

Re: Claude Code daily benchmarks for degradation tracking

#74
post #15
post #12

Simply search user prompts for curse words and then measure hostility sentiment. User hostility rises as agents fail to meet expectations.

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.

Re: Claude Code daily benchmarks for degradation tracking

#75
post #5

This is probably entirely down to subtle changes to CC prompts/tools. I've been using CC more or less 8 hrs/day for the past 2 weeks, and if anything it feels like CC is getting better and better at actual tasks. Edit: Before you downvote, can you explain how the model could degrade WITHOUT changes to the prompts? Is your hypothesis that Opus 4.5, a huge static model, is somehow changing? Master system prompt changin…

The easiest way would be to quantize the model, and serve different quants based on the current demand. Higher volumes == worse quant == more customers served per GPU

Re: Claude Code daily benchmarks for degradation tracking

#76
post #29

Why I do not believe this shows Anthropic serves folks a worse model: 1. The percentage drop is too low and oscillating, it goes up and down. 2. The baseline of Sonnet 4.5 (the obvious choice for when they have GPU busy for the next training) should be established to see Opus at some point goes Sonnet level. This was not done but likely we would see a much sharp decline in certain days / periods. The graph would look…

4. The graph starts January 8.

Why January 8? Was that an outlier high point?

IIRC, Opus 4.5 was released late november.

Re: Claude Code daily benchmarks for degradation tracking

#78
post #70

I have yet to experience any degradation in coding tasks I use to evaluate Opus 4.5, but I did see a rather strange and reproducible worsening in prompt adherence as part of none coding tasks since the third week of January. Very simple queries, even those easily answered via regular web searching, have begun to consistently not result accurate results with Opus 4.5, despite the same prompts previously yielding accur…

I definitely noticed a degradation, it feels regressed by a generation.

Re: Claude Code daily benchmarks for degradation tracking

#79
post #66

Earlier quoted context omitted.

noob question: why would increased demand result in decreased intelligence?

An operator at load capacity can either refuse requests, or move the knobs (quantization, thinking time) so requests process faster. Both of those things make customers unhappy, but only one is obvious.

This is intentional? I think delivering lower quality than what was advertised and benchmarked is borderline fraud, but YMMV.

Re: Claude Code daily benchmarks for degradation tracking

#80

[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.

The degradation may be more significant within the day than at the same time every day.
Post reply on HN