HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gunnarmorling
1brc
Java2024–2026
gunnarmorling / 1brc

1brc

1️⃣🐝🏎️ The One Billion Row Challenge -- A fun exploration of how quickly 1B rows from a text file can be aggregated with Java

34Distinct people
41Mentions
0Explicit recommenders
8.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

1️⃣🐝🏎️ The One Billion Row Challenge -- A fun exploration of how quickly 1B rows from a text file can be aggregated with Java

GitHub

Where it is used

No documented product use was verified in the last source check.

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, 7:27:27 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 month41 dated mentions

Observed mentions: 2024-01-02 11:43:54 UTC to 2026-06-03 18:29:03 UTC.

0510152024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 17 mentions; 2 submissions, 15 commentsJan 20242024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 20252025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 2026

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
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC17215
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC101
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC12012
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC303
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC000
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC000
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC000
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC303
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC000
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC000
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC000
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC000
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC000
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC202
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC101
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
1️⃣🐝🏎️ The One Billion Row Challenge Status Feb 4: The final leaderboards have been published. Congrats to all the winners, and a big thank you to everyone participating in this challenge as well as to everyone helping to organize it! Status Feb 3: All entries have been evaluated and I am in the process of finalizing the leaderboards. Status Feb 1: The challenge has been closed for new submissions. No new pull requests for adding submissions are accepted at this time. Pending PRs will be evaluated over the next few days. Status Jan 31: The challenge will close today at midnight UTC. Status Jan 12: As there has been such a large number of entries to this challenge so far (100+), and this is becoming hard to manage, please only create new submissions if you expect them to run in 10 seconds or less on the evaluation machine. Status Jan 1: This challenge is open for submissions! Sponsorship A big thank you to my employer Decodable for funding the evaluation environment and supporting this challenge! The One Billion Row Challenge (1BRC) is a fun exploration of how far modern Java can be pushed for aggregating one billion rows from a text file. Grab all your (virtual) threads, reach out to SIMD, optimize your GC, or pull any other trick, and create the fastest implementation for solving this task! The text file contains temperature values for a range of weather stations. Each row is one measurement in the format <string: station name>;<double: measurement>, with the measurement value having exactly one fractional digit. The following shows ten rows as an example: Hamburg;12.0 Bulawayo;8.9 Palembang;38.8 St. John's;15.2 Cracow;12.6 Bridgetown;26.9 Istanbul;6.2 Roseau;34.4 Conakry;31.2 Istanbul;23.0 The task is to write a Java program which reads the file, calculates the min, mean, and max temperature value per weather station, and emits the results on stdout like this (i.e. sorted alphabetically by station name, and the result values per station in the format <min>/<mean>/<max>, rounded to one fractional digit): {Abha=-23.0/18.0/59.2, Abidjan=-16.2/26.0/67.3, Abéché=-10.0/29.4/69.0, Accra=-10.1/26.4/66.4, Addis Ababa=-23.7/16.0/67.0, Adelaide=-27.8/17.3/58.5, ...} Submit your implementation by Jan 31 2024 and become part of the leaderboard! Results These are the results from running all entries into the challenge on eight cores of a Hetzner AX161 dedicated server (32 core AMD EPYC™ 7502P (Zen2), 128 GB RAM). # Result (m:s.ms) Implementation JDK Submitter Notes Certificates 1 00:01.535 link 21.0.2-graal Thomas Wuerthinger, Quan Anh Mai, Alfonso² Peterssen GraalVM native binary, uses Unsafe Certificate 2 00:01.587 link 21.0.2-graal Artsiom Korzun GraalVM native binary, uses Unsafe Certificate 3 00:01.608 link 21.0.2-graal Jaromir Hamala GraalVM native binary, uses Unsafe Certificate 00:01.880 link 21.0.1-open Serkan ÖZAL uses Unsafe Certificate 00:01.921 link 21.0.2-graal Van Phu DO GraalVM native binary, uses Unsafe Certificate 00:02.018 link 21.0.2-graal Stephen Von Worley GraalVM native binary, uses Unsafe Certificate 00:02.157 link 21.0.2-graal Roy van Rijn GraalVM native binary, uses Unsafe Certificate 00:02.319 link 21.0.2-graal Yavuz Tas GraalVM native binary, uses Unsafe Certificate 00:02.332 link 21.0.2-graal Marko Topolnik GraalVM native binary, uses Unsafe Certificate 00:02.367 link 21.0.1-open Quan Anh Mai uses Unsafe Certificate 00:02.507 link 21.0.1-open gonix uses Unsafe Certificate 00:02.557 link 21.0.1-open yourwass uses Unsafe Certificate 00:02.820 link 22.ea.32-open Li Lin uses Unsafe Certificate 00:02.995 link 21.0.2-graal tivrfoa GraalVM native binary, uses Unsafe Certificate 00:02.997 link 21.0.1-open gonix Certificate 00:03.095 link 21.0.2-graal Jamal Mulla GraalVM native binary, uses Unsafe Certificate 00:03.210 link 21.0.1-open Quan Anh Mai Certificate 00:03.298 link 21.0.1-graal Subrahmanyam uses Unsafe Certificate 00:03.431 link 21.0.1-graal Roman Musin GraalVM native binary, uses Unsafe Certificate 00:03.469 link 21.0.2-graal Elliot Barlas GraalVM native binary, uses Unsafe Certificate 00:03.698 link 21.0.1-graal Jason Nochlin Certificate 00:03.785 link 21.0.2-graal zerninv GraalVM native binary, uses Unsafe Certificate 00:03.820 link 21.0.2-graal John Ziamos GraalVM native binary, uses Unsafe Certificate 00:03.902 link 21.0.1-open Juan Parera Certificate 00:03.966 link 21.0.1-open Jin Cong Ho uses Unsafe Certificate 00:03.991 link 21.0.1-graal Vaidhy Mayilrangam uses Unsafe Certificate 00:04.066 link 21.0.1-open JesseVanRooy uses Unsafe Certificate 00:04.101 link 21.0.2-graal Jaime Polidura GraalVM native binary, uses Unsafe Certificate 00:04.209 link 21.0.1-open Giovanni Cuccu Certificate 00:04.474 link 21.0.1-open Roman Stoffel Certificate 00:04.676 link 21.0.2-tem Peter Levart Certificate 00:04.684 link 21.0.1-open Florin Blanaru uses Unsafe Certificate 00:04.701 link 21.0.1-open Dr Ian Preston Certificate 00:04.741 link 21.0.1-open Cliff Click uses Unsafe Certificate 00:04.800 link 21.0.1-open Parker Timmins Certificate 00:04.884 link 21.0.1-open Aleksey Shipilëv Certificate 00:04.920 link 21.0.1-graal Subrahmanyam Certificate 00:05.077 link 21.0.2-graal Jonathan Wright GraalVM native binary, uses Unsafe Certificate 00:05.142 link 21.0.1-open Arjen Wisse Certificate 00:05.167 link 21.0.2-open Yevhenii Melnyk Certificate 00:05.235 link 21.0.1-open unbounded Certificate 00:05.336 link java Sumit Chaudhary uses Unsafe Certificate 00:05.354 link 21.0.2-graal Arman Sharif GraalVM native binary, uses Unsafe Certificate 00:05.478 link 21.0.1-open Olivier Bourgain uses Unsafe Certificate 00:05.559 link 21.0.1-graal Panagiotis Drakatos GraalVM native binary Certificate 00:05.887 link 21.0.1-graal Charlie Evans uses Unsafe Certificate 00:05.979 link 21.0.1-graal Sam Pullara Certificate 00:06.166 link 21.0.1-ope
Read the full README on GitHub

What Hacker News says

17 sources
The official challenge is in Java, but there are unofficial solutions in the "Show and tell" categories, using other languages, databases, and stuff (even a Fortran solution that takes 3 seconds without going too far in optimization): https://github.com/gunnarmorling/1brc/discussions/categories... I like this discussion because while the original is about "what can you do in 2024 stock java", I'm more interested in "what can you do if you use naive, obvious solutions". AWK does this in 6 minutes but, as pointed in this comment: https://github.com/gunnarmorling/1brc/discussions/171#discus... > It's either 6 minutes with 20 lines of AWK written in five minutes. Or 6 seconds in 300 lines of java written in five days. Classic "XKCD: Is It Worth the Time?".
In One Billion Row Challenge Shows Java Can Process 1B Rows File in 2 Seconds
Even manual vectorization is pain...writing ASM, really? Rust has unstable portable SIMD and a few third-party crates, C++ has that as well, C# has stable portable SIMD and a small out of box BLAS-like library to help with most common tasks (like SoftMax, Magnitude and etc. on top of spans of floats over writing manually), hell it even exercises PackedSIMD when ran in a browser. And now Java is getting Panama vectors some time in the future (though the question of codegen quality stands open given planned changes to unsafe API). Go among these is uniquely disadvantaged. And if that's not enough, you may want to visit 1Brc's challenge discussions and see that Go struggles to get anywhere close to 2s mark with both C# and C++ blazing past it: https://hotforknowledge.com/2024/01/13/1brc-in-dotnet-among-... https://github.com/gunnarmorling/1b
Read the rest
In From slow to SIMD: A Go optimization story
In terms of performance: I realize that this is a somewhat "toy" issue, and it's a sample size of 1, but for the currently ongoing "One Billion Row Challenge"[1] (an ongoing Java performance competition related to parsing and aggregating a 13 GB file), all of the current top-performers are using Unsafe. More specifically, the use of Unsafe appears to have been the change for a few entries that allowed getting below the 3-second barrier in the test. 1. https://github.com/gunnarmorling/1brc
In JEP Draft: Deprecate memory-access methods in sun.misc.unsafe for removal
This has been super fun. My current PR[1] is another 15% faster than my entry in the README. Sadly I haven't been able to make any progress on using SIMD to accelerate any part of it. I think the issues with hashing could be easily covered by having the 500 city names in the test data also be randomly generated at test time. There is no way to ensure there aren't hash collisions without doing a complete comparison between the names. [1] https://github.com/gunnarmorling/1brc/pull/56
In The One Billion Row Challenge

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

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.