Benchmarking fixes: query 15, update validator, formatting, ray scheduling fix #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #81
Small fixes that came up during benchmarking.
util::exec_sql_on_tablesreplaced withutil::LocalValidatoras keeping state in its ownctxit can more easily handle multiple queriesray.remoteannotations to denote theSPREADscheduling strategyray.remoteto requirenum_cpus=0.01such that we do ask for a small amount of logical CPU, and this way can avoid being scheduled on the head nodeblack --line-length 79formatted pythonNote that DDL/DML statements, like in query 15, end up producing an empty physical plan and are sent to a
DFRayProcessorfor execution. This doesn't produce an incorrect result, but we should optimize this in a subsequent improvement.