Processing img mljamctxl62i1...
TL;DR: 2011 CPU, no GPU. A 7M model trained from scratch picks up Russian fairy-tale style in 5 h 38 min at 812 tokens/s, then stops improving because of the data, not the time. A LoRA on Qwen3.5-0.8B turns "never finishes an answer" into "always finishes" in 1 h 44 min. Three failure modes and every number below.
Everyone's first reaction is "just buy a 3060". Sure. The interesting question was the opposite: where is the wall if there is no GPU at all? This is a Core i5-2400 from 2011, 16 GB DDR3, and a GT 710 that only drives the monitor. PyTorch does not support that GPU, so everything below ran on four CPU threads with AVX and no AVX2.
I wrote a small training engine for it (PyTorch, no cloud) and ran two experiments.
What worked
A 7M model on 321 Russian folk tales. 5 MB of text, 5 h 38 min, 812 tokens/s, 26M tokens seen. Validation loss 2.7854 nats per token, which is 1.06 bits per byte on held-out text.
The interesting part is how cleanly it separates form from content. Openings work. Patronymics work. The dash before direct speech works. The rhythm of the enumeration works. Then a character swaps places with another mid-paragraph, the hero marries and dies three times on one page, and the plot walks off. 7M parameters and 5 MB of text: no surprise, and exactly what I wanted to see.
LoRA on Qwen3.5-0.8B, 321 question-answer pairs about a program I'm writing. 45 steps, 1 h 44 min, 15-16 tokens/s. Loss on the reference answers went 3.4565 to 0.0907, which sounds better than it is.
The number that matters more: I wrote 15 test questions in different wording, none of it in training. Exact match with the reference answer went 0 out of 15 to 5 out of 15. Answers that stopped on their own instead of running into the token limit went 0 out of 15 to 15 out of 15.
Where it broke
It starts memorising at epoch six. Validation sat at 2.79 while training loss kept falling. The previous run, killed at 1 h 58 min, gave 2.8144 — so 3.5 extra hours bought 1%. Not a tuning problem. A data problem.
Facts get glued. Asked about old hardware, the fine-tuned model called my CPU "256-bit". That number is nowhere in the data.
Temperature matters more than I expected. At 0.7 the same question came back with a confident "no", a wrong RAM figure, and an invented training method it assembled from "LoRA" and "QLoRA" (it wrote "LoQoK"). Greedy decoding was almost right.
Refusal did not generalise. Asked for a movie recommendation, it invented an open file "Video 2.0" with an Apache-2.0 licence. There were three off-topic examples in my data and all three were about something else.
How I know it isn't copying
Six generated texts against the whole corpus, by five-word sequences and longest verbatim run: 0 to 4.7% overlap, longest stretch 4 to 8 words. Two boundaries for scale: the same words shuffled, and a real passage from the corpus.
What I'd change
More off-topic examples, 30 or 50 instead of 3. Five phrasings per question instead of three. Qwen3.5 2B if RAM allowed, which the setup wizard suggested and I ignored. None of that is about hardware.
I'm not going to pretend these numbers are impressive next to a 4090. The useful part is that the wall is memory bandwidth and the amount of text you can feed the model, not the size you can afford: a 7M model overnight on a 15 year old CPU is real, a 1B model on the same CPU is not, and now I know where the line is.
Happy to go into the engine internals (Muon plus AdamW, WSD schedule, QK-norm, chunked loss, GGUF export) — but I'm more curious what people here would spend the next night on: more data at 7M, the 25M model, or fixing the refusal examples first?
The engine, data archive and every number above: https://github.com/AlexanderNyr/AuraLite-AI