r/mlscaling • • 7h ago

Announcing Artificial Analysis Intelligence Index v5

Thumbnail
artificialanalysis.ai
14 Upvotes

It features a fixed HLE, a fixed CritPT, and more.

Claude Opus 5.5 retained the top spot and saw no drop in its score. Astra and Sol 6.1 rescored significantly higher, rising from 6th to 2nd and from 9th to 3rd respectively. Gemini 4 Argon's score didn't fall by much, and it gained a rank (7th -> 6th) due to other models leaving the top 5.

The losers seem to have been the mid-sized models, China/Europe (Kimi K3.1 fell from 4th to 9th), and (surprisingly) Fable 5.1.


r/mlscaling • • 7h ago

N, T "Formalizing the Enormous Theorem: Axiom has formalized in Lean the classification of finite simple groups, the longest proof in the history of mathematics", Axiom

Thumbnail axiommath.ai
8 Upvotes

r/mlscaling • • 4h ago

N, Econ, MS, Hardware "Microsoft to Offer Buyouts to 60,000 [~25%] Workers in New Cost Cut", Bloomberg (to spend on AI datacenters instead)

Thumbnail
bloomberg.com
1 Upvotes

r/mlscaling • • 1d ago

[P] Self-distillation with an EMA teacher at scale: ZeRO-3 + PEFT

Thumbnail
5 Upvotes

r/mlscaling • • 1d ago

Deepity: a hand-tuned C++/CUDA predictive coding library, beats jpc (JAX) and ngc-learn on MNIST (CPU benchmarks + source inside) [P]

Thumbnail
1 Upvotes

r/mlscaling • • 2d ago

OP, Econ, Theory "Make or Buy: The Economics of Decision Models", Parth Parikh 2026

Thumbnail pncnmnp.github.io
3 Upvotes

r/mlscaling • • 2d ago

T Titans learns during inference. What if it learns the wrong thing?

Thumbnail
guttikondaparthasai.medium.com
0 Upvotes

Titans gives AI a separate neural memory that updates its own weights as information arrives.

I wrote a short visual explainer on how it works. In my small synthetic experiment, correcting false inputs improved recall—but didn’t fully restore it.

What should an AI be allowed to remember automatically—and how should we undo a mistake?


r/mlscaling • • 2d ago

We almost bought a second GPU for an OCR pipeline. Optimizing the existing one gave 15x instead. How often is “buy more hardware” the wrong fix?

Thumbnail
0 Upvotes

r/mlscaling • • 5d ago

How Cerebras Deploys Trillion-Parameter AI Models

Thumbnail
cerebras.ai
15 Upvotes

r/mlscaling • • 4d ago

R We fine-tuned every Qwen3.5 dense size (0.8B to 27B) with the same LoRA. 9B won, 27B lost to it. Nearly all the gain was learning to say no.

Thumbnail
0 Upvotes

r/mlscaling • • 5d ago

Exploring Open Problems in AI Routing: Beyond Classification and Confidence Scores

Thumbnail
0 Upvotes

r/mlscaling • • 6d ago

Title: I've been developing an experimental AI architecture called PNSN. I'd love technical feedback.

Thumbnail
0 Upvotes

r/mlscaling • • 6d ago

A 4B model that answers "how much?" with a distribution instead of a guessed number/text

Thumbnail
0 Upvotes

r/mlscaling • • 6d ago

N, OA, Hardware, Econ "As lame-duck battle over chips heats up, OpenAI pulls back: The artificial intelligence juggernaut once openly called for strict limits on sales of advanced chips to China"

Thumbnail politico.com
7 Upvotes

r/mlscaling • • 7d ago

N "Reorienting the Super Intelligence Frontier to Serve Americans", AFPI

Thumbnail
americafirstpolicy.com
11 Upvotes

r/mlscaling • • 6d ago

I've been developing an experimental AI architecture called PNSN. I'd love technical feedback.

Thumbnail
1 Upvotes

r/mlscaling • • 7d ago

Research idea: Can we reduce forgetting in recurrent LLM memory? Looking for critical feedback

Thumbnail
2 Upvotes

Research idea: Can we reduce forgetting in recurrent LLM memory? Looking for critical feedback

Hey everyone!

I'm an engineering student working on a research proposal about long-context LLMs and recurrent compressed memory. I'd really appreciate technical feedback from people working on LLMs, continual learning, recurrent architectures, or memory systems.

The core question: Can we train an LLM's memory to retain previously learned information while continuing to absorb new information?

I'm calling the proposed training method GMR (Generational Memory Retention) and the evaluation protocol STRATA.

This is still a pre-experimental proposal. I haven't run the experiments yet, so I'm looking for feedback before committing to the implementation.

1. The problem I'm interested in

Imagine an LLM processing a long stream of information in small chunks.

A chunk introduces the following fact:

"The Kestrel project uses Python 3.11."

Immediately after processing that chunk, the model can correctly answer:

"Which Python version does the Kestrel project use?"

Now imagine that the model processes hundreds of additional chunks. Its memory has a fixed capacity, and each new update modifies the existing memory state.

Eventually, the model might no longer answer the original question correctly, even though its model weights haven't changed during inference.

I'm calling this state-induced forgetting: information that was initially available becomes inaccessible after successive memory-state updates.

The key question is whether we can reduce this type of forgetting without simply increasing memory size.

2. STRATA: Measuring forgetting across memory updates

Most evaluations report accuracy at a particular context length or at the end of a conversation. I want to measure how the ability to retrieve individual facts changes as those facts get older.

The proposed protocol works roughly as follows:

Introduce facts into a recurrent memory system in successive context windows.

Record whether each fact can be retrieved immediately after it is introduced.

Evaluate the same facts again at increasing ages: 1, 2, 4, 8, 16, and progressively more memory updates.

Track performance out to hundreds of updates, with a planned maximum of 1,000.

Separate initial learning failures from facts that were initially learned but subsequently forgotten.

For example, if a system initially answers 90 out of 100 questions correctly, but answers only 60 correctly after many updates, that indicates a different failure from a system that answered only 60 correctly from the beginning.

I also want to test different kinds of facts:

Stable facts that never change.

Facts whose values are updated later.

Facts requiring reasoning across multiple earlier statements.

Facts mentioned only once.

The evaluation will report initial accuracy and age-dependent retention separately, rather than relying on a single final accuracy score.

3. GMR: Generational Memory Retention

The proposed training objective tries to preserve the ability to answer questions about facts that have already entered memory.

When a fact is first introduced, record the model's length-normalized log-likelihood for its correct answer. This becomes that fact's original score, or anchor.

After subsequent memory updates, calculate the score again. If it falls below the original score by more than an allowed margin, apply a penalty.

A simplified version of the retention loss is:

L_ret = (1 / B) * sum over sampled facts f of: max(0, anchor_f - margin - current_score_f)

Here:

anchor_f is the fact's original answer log-likelihood.

current_score_f is its current answer log-likelihood.

margin is the tolerated decrease before a penalty is applied.

B is the number of sampled facts.

L_ret is the retention loss.

The training objective also includes the usual language-model loss and an absorption loss that encourages learning newly introduced facts.

The intended effect is to discourage memory updates from damaging previously acquired answering capabilities while still allowing new information to enter memory.

An important mathematical observation

For the sampled facts whose current scores fall below their anchors by more than the margin, the gradient of this hinge loss is the same as the gradient from replaying those facts' correct answers.

Facts that have not regressed receive no retention gradient from this term.

This raises an important question: Does selecting replay examples according to their regression from their own original scores outperform ordinary replay or loss-prioritized replay under matched training budgets?

I don't want to assume that it does. That's one of the main things I want to test.

4. How I plan to evaluate it

The proposed experiments include the following configurations:

A baseline trained without an explicit retention objective.

A model using uniform replay of previously encountered facts.

A model using loss-prioritized replay.

A model using output distillation from a full-context reference.

A model using the proposed GMR objective.

The main comparison will use matched memory sizes, training streams, and replay budgets wherever possible.

I'll evaluate initial fact-learning accuracy, retention at different fact ages, the ability to learn new facts, the handling of updated information, and the computational cost.

The planned testbed is an associative recurrent memory on an open-weight backbone, with experiments at multiple fixed memory sizes.

For broader evaluation, I'm considering synthetic sequential streams, BABILong-derived data, LongMemEval sessions, and narrative documents with checked question-answer pairs.

The implementation and experiments have not started yet. All performance claims remain hypotheses.

5. What I want feedback on

I'd particularly appreciate critical feedback on these questions:

1. Is the problem formulation useful?

Is state-induced forgetting a meaningful way to isolate information loss caused by recurrent memory updates, or is this already adequately covered by existing work on recurrent memory, continual learning, and catastrophic forgetting?

2. Is GMR sufficiently different from ordinary replay?

Since the proposed loss effectively replays sampled facts that have regressed below their own anchors, is that distinction scientifically interesting? What additional theoretical analysis or experimental evidence would make the contribution convincing?

3. Is STRATA a useful evaluation protocol?

Would age-stratified measurements across hundreds of sequential memory updates reveal failure modes that existing long-context and conversational-memory evaluations might miss?

4. Are the experimental comparisons fair?

Which baselines would you consider essential? In particular, I'd like to compare GMR against ordinary replay, loss-prioritized replay, and output distillation without giving any method an unfair compute advantage.

5. What related work am I missing?

I'd appreciate pointers to papers on recurrent-state interference, memory retention, forgetting-aware replay, or training objectives that preserve information across sequential state updates.

Current status

This is a research proposal, not a completed result. My immediate priority is to validate the evaluation harness, establish whether measurable forgetting occurs in the chosen fixed-size memory system, and then test whether GMR improves on properly matched baselines.

I'm deliberately not claiming that the method works or that the idea is the first of its kind.

If you've worked on recurrent memory, compressed context, or continual learning, I'd genuinely value your criticism. I'd rather discover a fundamental flaw now than spend months implementing the wrong thing.

Thanks for reading!


r/mlscaling • • 7d ago

MiMo's tool-call repetition fix: why specialist RL + MOPD instead of direct targeted RL?

8 Upvotes

Reading MiMo-V2.6's write-up on tool-call repetition:

https://mimo.xiaomi.com/blog/mimo-v2-6-tool-call-repetition

Their fix is to collect repetition-prone contexts, train a specialist with single-turn RL + KL (positive reward only for no repetition AND no erroneous tool use), then integrate it into the main model through teacher-prefix MOPD. They report that the specialist already reaches zero replay repetition on their training and held-out sets after 12 steps (~7,000 examples).

What motivates the extra distillation stage? Why not continue RL directly on the mixed-RL checkpoint using those same contexts, reward and single-turn setup, then evaluate that repaired checkpoint? General-data replay or a retention objective could be added if other capabilities regress.

I mean a short, targeted repair run. The blog's estimated $2.31M full-MixRL alternative follows an earlier experiment with a stricter tool-call-count cap on a general data source; that does not seem to be a matched comparison with targeted RL on repetition cases.

I also realize the mixed-RL checkpoint and final MOPD model are different starting points. A useful control would be targeted RL starting from the integrated main model, compared against specialist RL + MOPD with initialization/stage effects accounted for.

Has anyone seen an ablation comparing repetition, downstream task performance and compute under matched repair data/reward? Does OPD provide a measurable retention/generalization benefit here, or is its main advantage fitting the existing multi-teacher pipeline? Would appreciate pointers or experience with similar behavioral repairs.

English translation/polishing assisted by an LLM.


r/mlscaling • • 7d ago

We used Claude to invent Scorpion anti-venom -- Citrini Research

Thumbnail
go.citrini.com
17 Upvotes

To separate hype from reality, we spent 3 months working firsthand with Anthropic's internal research model to see if it could create an experimental scorpion antivenom.

Introducing Citrini Therapeutics.


r/mlscaling • • 7d ago

I got tired of doing LLM cost math in spreadsheets, so I built a calculator.

Thumbnail
0 Upvotes

r/mlscaling • • 7d ago

N, T "Diffusion at Scale: Introducing Mercury 3"

Thumbnail
inceptionlabs.ai
2 Upvotes

r/mlscaling • • 8d ago

I built STROT: An open "decision compiler": an LLM writes the pipeline once, then a model makes every decision locally — $0/record, no API at runtime

Thumbnail
1 Upvotes

r/mlscaling • • 8d ago

[P] BitLens: Visual profiler for neural network quantization (Outlier ratio Omega, per-layer SQNR,MCU SRAM liveness, and 1-click torchao/ORT/TFLM config export)

Thumbnail
1 Upvotes

r/mlscaling • • 8d ago

Validation techniques for neural network models

Thumbnail
1 Upvotes

r/mlscaling • • 9d ago

Do you remnber SETI@Home : HiveMind: Decentralized Branch-Train-Mix Sparse MoE Upcycling & Speculative Swarm Inference over Consumer GPUs via DiLoCo-QLoRA and BOINC - Starting on old RTX 2070 !!! Let's build together HiveMind@Home

Post image
1 Upvotes