HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
geerlingguy
top500-benchmark
Jinja2023–2026
geerlingguy / top500-benchmark

top500-benchmark

Automated Top500 benchmark for clusters or single nodes.

4Distinct people
8Mentions
0Explicit recommenders
429GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Automated Top500 benchmark for clusters or single nodes.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 11:39:46 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2023-01-24 14:07:53 UTC to 2026-08-09 00:00:57 UTC.

012342023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

2 sources
Nice and organised work! My only reservation wrt the core of it is that it tests the cpus on a matrix operations task, and power efficiency in this case refers specifically to doing matrix operations. This is fine if that's the kind of task one wants to optimise for, but it does not necessarily translate to general energy efficiency for a broader spectrum of tasks that most people may do most of the time. And thus, if one wants to optimise for matrix operations, wouldn't it make sense to use apple's accelerate framework instead of blis/openblas (I think you used blis?)? I compiled hpl to use accelerate [0] on my m1 max (macbook), and ran it with settings almost identical to the original m1 max settings [1]. I get 422 Gflops vs 264 Gflops in m1 max mac studio (docker) [2]. My average draw (using a wall power meter, but not interfaced with
Read the rest
computer to keep a log, just me looking at it) is around 55-57W (probably less because it peaked at 57W but the last half was getting around 52W). With the most conservative estimate of 57W, this gave a 7.4 Gflops/W which is second place, just below the m4 mac mini in the benchmark table. The m1 max in the original did 4 Gflops/W (at 66W). So tbh I do not really trust the conclusion of the benchmark page, except if I miss sth. It is quite nice, organised work anyway. [0] https://github.com/tycho/hpl/blob/master/setup/Make.MacOSX_A... [1] I just fixed the p:q ratio, which was prob not really meant to be 1:10 there, I assume, also judging from the settings in the other tests. I put p=2,q=4. Also I was unable to put more than 8 processes in total. [2] The original m1 max benchmark: https://github.com/geerlingguy/top500-benchmark/issues/4
In Can Intel finally beat ARM on performance per Watt?
Not only that, the efficiency (FP64, HPL) is also beating all the M4/M3/M2/M1 systems I've tested besides the M4 Mac mini: https://github.com/geerlingguy/top500-benchmark#results I think the bigger news is Intel's made a chip that isn't just pushing clocks to hit some performance number, they've actually tuned clocks for efficiency... which also leads to much better battery life. And the fan on the system in the original article[1] also allows the Intel system to run substantially faster for longer tasks (where the Neo thermally saturates and has to stay throttled). (The iGPU is another matter... sadly still a bit lacking.) I'm hoping Intel makes a follow-up to the N100-series chips with just four of their newer low power E-cores. [1] https://www.jeffgeerling.com/blog/2026/excited-for-intel-eff...
In Can Intel finally beat ARM on performance per Watt?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.