Try more chunks than threads, and of different sizes

[tivrfoa]

/**
 * Solution based on thomaswue solution, commit:
 * commit d0a28599c293d3afe3291fc3cf169a7b25ae9ae6
 * Author: Thomas Wuerthinger
 * Date:   Sun Jan 21 20:13:48 2024 +0100
 *
 * The goal here was to try to improve the runtime of his 10k
 * solution of: 00:04.516
 *
 * With Thomas latest changes, his time is probably much better
 * already, and maybe even 1st place for the 10k too.
 * See: https://github.com/gunnarmorling/1brc/pull/606
 *
 * But as I was already coding something, I'll submit just to
 * see if it will be faster than his *previous* 10k time of
 * 00:04.516
 *
 * Changes:
 *   It's a similar idea of my previous solution, that if you split
 * the chunks evenly, some threads might finish much faster and
 * stay idle, so:
 *   1) Create more chunks than threads, so the ones that finish first
 * can do something;
 *   2) Decrease chunk sizes as we get closer to the end of the file.
 */

Check List:

• [x] You have run ./mvnw verify and the project builds successfully

• [x] Tests pass (./test.sh <username> shows no differences between expected and actual outputs)

• [x] All formatting changes by the build are committed

• [x] Your launch script is named calculate_average_<username>.sh (make sure to match casing of your GH user name) and is executable

• [x] Output matches that of calculate_average_baseline.sh

• [x] For new entries, or after substantial changes: When implementing custom hash structures, please point to where you deal with hash collisions (line number): not a new entry

• Execution time:

• Execution time of reference implementation:

Times for 220 million rows for the 10k, but the times on my machine are not good indicators ...

time ./target/CalculateAverage_thomaswue_image > thomas.out

real    0m5,239s
user    0m0,000s
sys 0m0,013s

time ./target/CalculateAverage_tivrfoa_image > me.out

real    0m4,810s
user    0m0,000s
sys 0m0,021s

[gunnarmorling]

00:02.205 now, nice!