惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
Microsoft Azure Blog
Microsoft Azure Blog
Jina AI
Jina AI
Hugging Face - Blog
Hugging Face - Blog
A
About on SuperTechFans
Y
Y Combinator Blog
D
DataBreaches.Net
I
InfoQ
Recent Announcements
Recent Announcements
Last Week in AI
Last Week in AI
G
Google Developers Blog
博客园_首页
博客园 - 司徒正美
V
V2EX
Stack Overflow Blog
Stack Overflow Blog
博客园 - 叶小钗
Engineering at Meta
Engineering at Meta
Apple Machine Learning Research
Apple Machine Learning Research
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
B
Blog
MongoDB | Blog
MongoDB | Blog
博客园 - 【当耐特】
D
Docker
量子位

Hacker News: Show HN

PurrrrrFocus: Pomodoro Timer App - App Store Workflow Engine — Multi-Step Orchestration for Bun RapidPhoto: Pro Photo Editor App - App Store GitHub - DheerG/swarms: Achieve extraordinary results with claude code across a variety of tasks SPICE simulation → oscilloscope → verification with Claude Code — Lucas Gerads Show HN: VCoding – A 5 MB native Windows IDE with no dynamic dependencies Show HN: LLMs don't hallucinate because they're bad at math, it's the format GitHub - Agent-FM/agentfm-core: AgentFM is a peer-to-peer network that turns everyday computers into a decentralized AI supercomputer. AgentFM lets you run massive AI workloads directly across a global mesh of idle CPUs and GPUs. Show HN: Tracking Top US Science Olympiad Alumni over Last 25 Years GitHub - Potarix/agent-hub: One place to talk to all your agents Show HN: Runtime security for AI agents(injection,tool abuse, data exfiltration) GitHub - dubeyKartikay/lazyspotify: Terminal Spotify client for macOS and Linux GitHub - the-banana-tool/king-louie: Easy to use GUI Personal AI Assistant. Win/Linux/Mac. Show HN I made my vacation rental bookable by AI agents–no Airbnb, 0% commission GitHub - basteez/jsf-autoreload: maven plugin to enable hot reload on jsf projects uvm32/hosts/host-gdbstub at main · ringtailsoftware/uvm32 GitHub - labsai/EDDI: Config-driven engine that turns JSON into production-grade AI agents. Multi-agent orchestration, 12+ LLM providers, MCP/A2A protocols, RAG, persistent memory, and enterprise compliance (EU AI Act, GDPR, HIPAA). Built on Quarkus. GitHub - glitchnsec/fortyone-oss: AI Executive Assistant Platform Quickstart | Alien GitHub - muxshed/shed: One stream in, or many. Every destination, simultaneously. No cloud middleman, no per-channel fees, no limits. GitHub - ocrbase-hq/ocrbase: 📄 PDF/IMG ->.MD/JSON Document OCR API for PaddleOCR and GLMOCR. Self-hostable. GitHub - impactjo/home-memory: MCP server that lets your AI assistant remember everything about your home. GitHub - Sets88/dbcls: DbCls is a powerful terminal database client that supports various databases GitHub - neptun2000/heor-agent-mcp GitHub - SeanFDZ/macmind: Single-layer transformer in HyperTalk for the classic Macintosh RollQuation: Math Puzzles - Apps on Google Play GitHub - dropbox/witchcraft Show HN: Agent-cache – Multi-tier LLM/tool/session caching for Valkey and Redis GitHub - opentalon/opentalon: OpenTalon is an open-source platform built from the ground up in Go as a robust alternative to OpenClaw LinkedIn™ 职位抓取工具 - Chrome 应用商店
GitHub - sammysltd/euromesh: A sourced model and short re...
smashini · 2026-06-15 · via Hacker News: Show HN

A sourced model and short report on a single question:

Can Europe stand up a sovereign frontier-class AI model now, by federating the public compute it already owns, while the gigawatt datacenters it is planning take years to connect to the grid?

The answer the model gives is yes, as a stopgap. Europe already operates tens of exaflops of public AI compute across the EuroHPC supercomputers and the national AI Factories. A 1 GW campus, by contrast, waits a mean of 7.6 years for grid power. Federated with low-communication (DiLoCo-style) training, the compute Europe already has can deliver a frontier-class model around 2028, against around 2033 for a new gigawatt campus.

Read this first

The report is paper/compute-at-home.pdf (built from paper/compute-at-home.md). It is a short, sourced read aimed at a general audience. Title: "Do We Need OpenAI or Anthropic? Europe Has Tens of Exaflops at Home."

What is in the repo

euromesh/
├── README.md
├── requirements.txt
├── paper/
│   ├── compute-at-home.md / .pdf   the report
│   ├── grid_queue_dataset.md       sourced 1 GW vs 40 MW grid-connection lead times
│   ├── eurohpc_substrate.md        sourced EU public-compute inventory + "is it enough" math
│   ├── build_pdf.sh, _report.typ   PDF build (pandoc + typst)
│   └── figures/                    generated charts (PNG + SVG)
└── model/
    ├── MODEL_SPEC.md               the model specification (equations, params, invariants)
    ├── RESULTS.md                  full results, scenarios, sensitivity, caveats
    ├── run.py                      regenerates every CSV and figure
    ├── src/                        the three-layer model (efficiency, ramp, regions)
    ├── params/                     hardware.yaml, training.yaml, regions.csv + SOURCES
    ├── results/                    generated CSVs (do not hand-edit)
    └── tests/                      pytest suite (52 tests) + invariant self-checks

The model in one paragraph

Three layers. Layer 1 is the per-FLOP efficiency of low-communication training (how much the DiLoCo penalty costs). Layer 2 is time-to-availability (when sites energize and how fast cumulative compute accrues). Layer 3 is a per-region scorecard on time, cost, carbon, and feasibility. The headline result is set almost entirely by Layer 2: it reduces to one inequality, the federation wins if its sites are online before a gigawatt campus is. The training efficiency penalty is second-order, confirmed by the sensitivity tornado.

Run it

python3 -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/python -m model.run          # regenerates all CSVs in model/results and figures in paper/figures
.venv/bin/python -m pytest model/tests/ # 52 passed
bash paper/build_pdf.sh                 # rebuilds paper/compute-at-home.pdf (needs pandoc + typst)

The run is reproducible from a clean tree: deleting every output and re-running exits 0 and regenerates everything.

Data and sources

  • Grid-connection lead times: paper/grid_queue_dataset.md, seven regions, per-region primary sources, anchored by the AWS "up to seven years" statement and the IEA 2-to-10-year range, with limitations stated.
  • EU public compute: paper/eurohpc_substrate.md, the EuroHPC flagships and the 19 AI Factories, accelerator counts and the training-time math.
  • Model parameters: model/params/SOURCES.md and model/params/SOURCES_hardware_training.md, with confidence tags.

Honest caveats

The point of this repo is clarity, not novelty. The thesis rests on grid-queue lead times, which are sourced central estimates rather than observed figures (no European operator has yet energized a 1 GW point load). The compute is owned but not yet usable for one coordinated run: the EuroHPC machines are shared, batch-scheduled, and heterogeneous, so the addressable fraction is a political decision rather than a hardware fact. Frontier-scale distributed training is unproven above about 10B parameters today, so the target is a credible frontier-class model rather than a guaranteed 405B. All of this is in model/RESULTS.md and the report's caveats section. Figures and dated events are as of June 2026. This is an independent model and analysis, not peer-reviewed.