From eceaf1868d5d541a03b65bf3a04861b6e1837960 Mon Sep 17 00:00:00 2001 From: Robin Moffatt Date: Wed, 3 Jan 2024 15:30:36 +0000 Subject: [PATCH] Add note about sharing non-Java solutions on GH discussions; Also fixing millisecond separator Co-authored-by: Gunnar Morling --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f52fdb3..e1f6579 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ Submit your implementation by Jan 31 2024 and become part of the leaderboard! ## Results -| # | Result (m:s:ms) | Implementation | JDK | Submitter | +| # | Result (m:s.ms) | Implementation | JDK | Submitter | |---|-----------------|--------------------|-----|---------------| | 1.| 00:14.848| [link](https://github.com/gunnarmorling/1brc/blob/main/src/main/java/dev/morling/onebrc/CalculateAverage_spullara.java)| 21.0.1-graalce| [Sam Pullara](https://github.com/spullara)| | 2.| 00:16.558| [link](https://github.com/gunnarmorling/1brc/blob/main/src/main/java/dev/morling/onebrc/CalculateAverage_ebarlas.java)| 21.0.1-open| [Elliot Barlas](https://github.com/ebarlas)| @@ -120,7 +120,7 @@ To submit your own implementation to 1BRC, follow these steps: * The execution time of the program on your system and specs of the same (CPU, number of cores, RAM). This is for informative purposes only, the official runtime will be determined as described below. * I will run the program and determine its performance as described in the next section, and enter the result to the scoreboard. -**Note:** I reserve the right to not evaluate specific submissions if I feel doubtful about the implementation (I.e. I won't run your BitCoin miner ;). +**Note:** I reserve the right to not evaluate specific submissions if I feel doubtful about the implementation (I.e. I won't run your Bitcoin miner ;). If you'd like to discuss any potential ideas for implementing 1BRC with the community, you can use the [GitHub Discussions](https://github.com/gunnarmorling/onebrc/discussions) of this repository. @@ -154,6 +154,9 @@ A: No, this challenge is focussed on Java only. Feel free to inofficially share _Q: Can I use non-JVM languages and/or tools?_\ A: No, this challenge is focussed on Java only. Feel free to inofficially share interesting implementations and results though. For instance it would be interesting to see how DuckDB fares with this task. +_Q: I've got an implementation—but it's not in Java. Can I share it somewhere?_\ +A: Whilst non-Java solutions cannot be formally submitted to the challenge, you are welcome to share them over in the [Show and tell](https://github.com/gunnarmorling/1brc/discussions/categories/show-and-tell) GitHub discussion area. + _Q: Can I use JNI?_\ A: Submissions must be completely implemented in Java, i.e. you cannot write JNI glue code in C/C++. You could use AOT compilation of Java code via GraalVM though, either by AOT-compiling the entire application, or by creating a native library (see [here](https://www.graalvm.org/22.0/reference-manual/native-image/ImplementingNativeMethodsInJavaWithSVM/).