72.24 minutes to GPT-2 on 8×H100.
AutoTrust's ScienceGuru, running Guru Turbo 1.2, posted the fastest result we've found on
@karpathy 's Time-to-GPT-2 benchmark (one run, self-reported): 27% under the official record and 9.6 min ahead of the best community recipe.
The field
Reported times on the official leaderboard and in public nanochat PRs, as of Sept 24:
- 72.24 min · ScienceGuru (AutoTrust) · 1 run
- 81.84 min · Giovanni Zinzi · 6 runs
- 91.74 min · Oriole Networks · 3 runs
- 94.58 min · Martin Jurča (
Seznam.cz) · 6 runs
- 94.6 min · Weco-optimized run · 3 runs
- ~99 min · Official record, Karpathy's autoresearch round 2 · 5 runs
Zinzi also reported a 73.92-min experiment with a Cosmopedia data mix (3 runs), which he set aside after it regressed at a smaller model size.
The lead
- 27% faster than the official record (−26.8 min)
- 12% faster than the best community recipe (−9.6 min)
- 19–22 min ahead of Oriole Networks,
Seznam.cz and the Weco-optimized run
How
Starting from nanochat and Zinzi's d22 recipe,
@ScienceGuruAI narrowed the MLP (5,120 → 4,864) and set a 9,841-step training horizon. FP8, FlashAttention 3 and Muon/AdamW are unchanged. CORE: 0.259212, above GPT-2's 0.256525.
Why it matters
The official record came from Karpathy's own autoresearch agents. Ours was researched and coded by ScienceGuru: an AI improving how LLMs are trained, the core loop of recursive self-improvement. ScienceGuru already runs that loop on the training of our own Guru models.
It's our fourth public RSI result this month, after #1 on Autoresearch@Home, the validated lead on
@MedARC_AI 's NanoPath v2 and 24.90 s on NanoGPT Speedrun. Not bad for a tiny Singapore startup.
Caveats: one run (seed 42), self-reported, not yet on the official leaderboard. Code, logs and source hashes are open, and we'd welcome independent reproduction.
Built on
@karpathy's nanochat and Giovanni Zinzi's open recipe. Thanks to everyone pushing this benchmark forward.
Code:
github.com/AutoTrustAI/gpt2-…
Try ScienceGuru:
scienceguru.ai
ALT 72.24 minutes to GPT-2 on 8×H100.
AutoTrust's ScienceGuru, running Guru Turbo 1.2, posted the fastest result we've found on Andrej Karpathy's Time-to-GPT-2 benchmark (one run, self-reported): 27% under the official record and 9.6 min ahead of the best community recipe.
The field
Reported times on the official leaderboard and in public nanochat PRs, as of Sept 24:
- 72.24 min · ScienceGuru (AutoTrust) · 1 run
- 81.84 min · Giovanni Zinzi · 6 runs
- 91.74 min · Oriole Networks · 3 runs
- 94.58 min · Martin Jurča (Seznam.cz) · 6 runs
- 94.6 min · Weco-optimized run · 3 runs
- ~99 min · Official record, Karpathy's autoresearch round 2 · 5 runs
Zinzi also reported a 73.92-min experiment with a Cosmopedia data mix (3 runs), which he set aside after it regressed at a smaller model size.
The lead
- 27% faster than the official record (−26.8 min)
- 12% faster than the best community recipe (−9.6 min)
- 19–22 min ahead of Oriole Networks, Seznam.cz and the Weco-optimized run
How
Starting fr
ALT 72.24 minutes to GPT-2 on 8×H100.
AutoTrust's ScienceGuru, running Guru Turbo 1.2, posted the fastest result we've found on Andrej Karpathy's Time-to-GPT-2 benchmark (one run, self-reported): 27% under the official record and 9.6 min ahead of the best community recipe.
The field
Reported times on the official leaderboard and in public nanochat PRs, as of Sept 24:
- 72.24 min · ScienceGuru (AutoTrust) · 1 run
- 81.84 min · Giovanni Zinzi · 6 runs
- 91.74 min · Oriole Networks · 3 runs
- 94.58 min · Martin Jurča (Seznam.cz) · 6 runs
- 94.6 min · Weco-optimized run · 3 runs
- ~99 min · Official record, Karpathy's autoresearch round 2 · 5 runs
Zinzi also reported a 73.92-min experiment with a Cosmopedia data mix (3 runs), which he set aside after it regressed at a smaller model size.
The lead
- 27% faster than the official record (−26.8 min)
- 12% faster than the best community recipe (−9.6 min)
- 19–22 min ahead of Oriole Networks, Seznam.cz and the Weco-optimized run
How
Starting fr
ALT 72.24 minutes to GPT-2 on 8×H100.
AutoTrust's ScienceGuru, running Guru Turbo 1.2, posted the fastest result we've found on Andrej Karpathy's Time-to-GPT-2 benchmark (one run, self-reported): 27% under the official record and 9.6 min ahead of the best community recipe.
The field
Reported times on the official leaderboard and in public nanochat PRs, as of Sept 24:
- 72.24 min · ScienceGuru (AutoTrust) · 1 run
- 81.84 min · Giovanni Zinzi · 6 runs
- 91.74 min · Oriole Networks · 3 runs
- 94.58 min · Martin Jurča (Seznam.cz) · 6 runs
- 94.6 min · Weco-optimized run · 3 runs
- ~99 min · Official record, Karpathy's autoresearch round 2 · 5 runs
Zinzi also reported a 73.92-min experiment with a Cosmopedia data mix (3 runs), which he set aside after it regressed at a smaller model size.
The lead
- 27% faster than the official record (−26.8 min)
- 12% faster than the best community recipe (−9.6 min)
- 19–22 min ahead of Oriole Networks, Seznam.cz and the Weco-optimized run
How
Starting fr