-
Notifications
You must be signed in to change notification settings - Fork 328
[Doc] Tpch Benchmark Instructions #3
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
Closed
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,55 @@ | ||
Benchmarking | ||
=== | ||
|
||
# Generate Data | ||
> *TODO* instructions to be provided | ||
# Instructions | ||
## CSharp | ||
1. Ensure that the Microsoft.Spark.Worker is properly [installed](https://github.com/dotnet/spark/tree/master/deployment#cloud-deployment) in your cluster. | ||
2. Build `microsoft-spark-<spark_majorversion.spark_minorversion.x>-<spark_dotnet_version>.jar` and the [csharp tpch benchmark](csharp/Tpch) application by following the [build instructions](../docs/building). | ||
3. Upload [run_csharp_benchmark.sh](run_csharp_benchmark.sh), the Tpch benchmark application, and `microsoft-spark-<spark_majorversion.spark_minorversion.x>-<spark_dotnet_version>.jar` to the cluster. | ||
4. Run the benchmark by invoking `run_csharp_benchmark.sh` | ||
```shell | ||
run_csharp_benchmark.sh \ | ||
<num_executors> \ | ||
<driver_memory> \ | ||
<executor_memory> \ | ||
<executor_cores> \ | ||
</path/to/Tpch.dll> \ | ||
</path/to/microsoft-spark-<spark_majorversion.spark_minorversion.x>-<spark_dotnet_version>.jar> \ | ||
</path/to/Tpch executable> \ | ||
</path/to/dataset> \ | ||
<number of iterations> \ | ||
<true for sql tests, false for functional tests> | ||
``` | ||
|
||
## Python | ||
1. Upload [run_python_benchmark.sh](run_python_benchmark.sh) and all [python tpch benchmark](python/) files to the cluster. | ||
2. Run the benchmark by invoking `run_python_benchmark.sh` | ||
```shell | ||
run_python_benchmark.sh \ | ||
<num_executors> \ | ||
<driver_memory> \ | ||
<executor_memory> \ | ||
<executor_cores> \ | ||
</path/to/tpch.py> \ | ||
</path/to/dataset> \ | ||
<number of iterations> \ | ||
<true for sql tests, false for functional tests> | ||
``` | ||
|
||
## Scala | ||
1. `mvn package` to build the [scala tpch benchmark](scala/) application. | ||
2. Upload [run_scala_benchmark.sh](run_scala_benchmark.sh) and the `microsoft-spark-benchmark-<version>.jar` to the cluster. | ||
3. Run the benchmark by invoking `run_scala_benchmark.sh` | ||
```shell | ||
run_scala_benchmark.sh \ | ||
<num_executors> \ | ||
<driver_memory> \ | ||
<executor_memory> \ | ||
<executor_cores> \ | ||
</path/to/microsoft-spark-benchmark-<version>.jar> \ | ||
</path/to/dataset> \ | ||
<number of iterations> \ | ||
<true for sql tests, false for functional tests> | ||
``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
#!/bin/bash | ||
|
||
NUM_EXECUTORS=$1 | ||
DRIVER_MEMORY=$2 | ||
EXECUTOR_MEMORY=$3 | ||
EXECUTOR_CORES=$4 | ||
CSHARP_DLL=$5 | ||
JAR_PATH=$6 | ||
CSHARP_EXECUTABLE=$7 | ||
DATA_PATH=$8 | ||
NUM_ITERATION=$9 | ||
IS_SQL=$10 | ||
|
||
for i in {1..22} | ||
do | ||
$SPARK_HOME/bin/spark-submit --master yarn --num-executors $NUM_EXECUTORS --driver-memory $DRIVER_MEMORY --executor-memory $EXECUTOR_MEMORY --executor-cores $EXECUTOR_CORES --files $CSHARP_DLL --class org.apache.spark.deploy.DotnetRunner $JAR_PATH $CSHARP_EXECUTABLE $DATA_PATH $i $NUM_ITERATION $IS_SQL | ||
done |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
#!/bin/bash | ||
|
||
NUM_EXECUTORS=$1 | ||
DRIVER_MEMORY=$2 | ||
EXECUTOR_MEMORY=$3 | ||
EXECUTOR_CORES=$4 | ||
PYTHON_SCRIPT=$5 | ||
DATA_PATH=$6 | ||
NUM_ITERATION=$7 | ||
IS_SQL=$8 | ||
|
||
for i in {1..22} | ||
do | ||
$SPARK_HOME/bin/spark-submit --master yarn --num-executors $NUM_EXECUTORS --driver-memory $DRIVER_MEMORY --executor-memory $EXECUTOR_MEMORY --executor-cores $EXECUTOR_CORES $PYTHON_SCRIPT $DATA_PATH $i $NUM_ITERATION $IS_SQL | ||
done |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
#!/bin/bash | ||
|
||
NUM_EXECUTORS=$1 | ||
DRIVER_MEMORY=$2 | ||
EXECUTOR_MEMORY=$3 | ||
EXECUTOR_CORES=$4 | ||
JAR_PATH=$5 | ||
DATA_PATH=$6 | ||
NUM_ITERATION=$7 | ||
IS_SQL=$8 | ||
|
||
for i in {1..22} | ||
do | ||
$SPARK_HOME/bin/spark-submit --master yarn --num-executors $NUM_EXECUTORS --driver-memory $DRIVER_MEMORY --executor-memory $EXECUTOR_MEMORY --executor-cores $EXECUTOR_CORES --class com.microsoft.tpch.App $JAR_PATH $DATA_PATH $i $NUM_ITERATION $IS_SQL | ||
done |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a description on what the field of result means? Along with warm description? Also, do we plan to get rid of cold mechanism all together (looks like that is happening in the code)?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can get the cold mechanism by surrounding the spark-submit with another for loop and sending 1 as the number of iterations to the application.