aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGunnar Morling <gunnar.morling@googlemail.com>2024-01-06 14:33:35 +0100
committerGitHub <noreply@github.com>2024-01-06 14:33:35 +0100
commita3626e589f4a3885f2d073b28728b4fdd56a1d04 (patch)
tree06f58bda7deab496459582297d512b8831a2c39c
parent580a30d3d76fb0ec28f771d8835584e74b83bc4e (diff)
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 380e4f8..8ac0d64 100644
--- a/README.md
+++ b/README.md
@@ -222,7 +222,7 @@ A: Yes, you can. The primary focus of the challenge is about learning something
_Q: Which operating system is used for evaluation?_\
A: Fedora 39.
-_Q: My solution runs on 2 sec on my machine. Am I the fastest 1BRC-er in the world?_\
+_Q: My solution runs in 2 sec on my machine. Am I the fastest 1BRC-er in the world?_\
A: Probably not :) 1BRC results are reported in wallclock time, thus results of different implementations are only comparable when obtained on the same machine. If for instance an implementation is faster on a 32 core workstation than on the 8 core evaluation instance, this doesn't allow for any conclusions. When sharing 1BRC results, you should also always share the result of running the baseline implementation on the same hardware.
_Q: Why_ 1️⃣🐝🏎️ _?_\