-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dpsoft: first submission #572
Conversation
Please run |
@gunnarmorling done! |
There's a test failure, please see CI for details. |
@gunnarmorling sorry, done! |
Getting differences for the 1B rows file now:
|
Looking good for the regular 1B file now, but it fails with the 10K key set (see create_measurements3.sh):
|
Running out of heap space now with 10K keys:
|
@gunnarmorling It seems like the issue lies in the size of the segments, when running the code on my machine it throws an exception related to the size exceeding Integer.MAX_VALUE, while on the test machine, it fails with an "underflow" error. I've fixed(i think so) the issue and conducted tests using the following approach:
and finally:
|
Similar error as before. Note that test runs on 32 machines, you should be able to reproduce the issue by using that many chunks rather than relying on CPU count on your machine.
|
@gunnarmorling fixed! |
Hum, hum. So all tests pass now, it also passes the 10K keyset, but it's way too fast, finishing in 100ms (current fastest one is 2.7 sec). I feel it may somehow skip portions if the file? |
@gunnarmorling I'll take a look |
@gunnarmorling Indeed was truncating the file because it was looking at the segment size instead of the file size. |
Same thing as before, it seems to skip parts, 100ms for the 10K key set case:
|
@gunnarmorling the file is created with ./create_measurements3.sh 1000000000? and using eight cores for the evaluation? |
Looking good now: 00:06.392. Passing for 10K keyset too. |
@gunnarmorling Thank you so much for the initiative. I would have liked to have had more free cpu cycles to improve my solution. Perhaps next time! :) |
Hehe, yeah, understood. Unfortunately, I had to make a cut-off date to keep
the effort for running it in check. Next time :)
… Message ID: ***@***.***>
|
Check List:
./test.sh <username>
shows no differences between expected and actual outputs)calculate_average_<username>.sh
(make sure to match casing of your GH user name) and is executablecalculate_average_baseline.sh