You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. Create the `/flash23` folder. Copy `bpc_t93586_s2_synthetic_5GB`
@@ -408,7 +408,7 @@ Note that SparkBench mini does not require the high I/O throughput
408
408
409
409
5. Run `spark_standalone_remote_mini` job on a real machine.
410
410
This will create data in `/flash23/warehouse`
411
-
and `<benchpressPath>/benchmarks/spark_standalone/spark-2.4.5-bin-hadoop2.7/metastore_db`.
411
+
and `<benchpressPath>/benchmarks/spark_standalone/spark-4.0.0-bin-hadoop3/metastore_db`.
412
412
Create a backup of these two folders. By default, this job uses the 5GB dataset.
413
413
If you want to use the 1GB dataset, run the job with specifying the
414
414
`dataset_name` parameter like this:
@@ -425,12 +425,12 @@ with the same commands and options.
425
425
Building database takes a considerable amount of time, so it's advisable to consider
426
426
using the same set of storage nodes and NVMe drives when running SparkBench on another
427
427
compute node server. If you choose to reuse the Spark database in `/flash23/warehouse`,
428
-
please also make sure to copy the folder `metastore_db` under `benchmarks/spark_standalone/spark-2.4.5-bin-hadoop2.7`
428
+
please also make sure to copy the folder `metastore_db` under `benchmarks/spark_standalone/spark-4.0.0-bin-hadoop3`
429
429
to the new machine's same location, for example:
430
430
431
431
```
432
432
# Under the DCPerf folder
433
-
rsync -a benchmarks/spark_standalone/spark-2.4.5-bin-hadoop2.7/metastore_db root@<target-hostname>:~/DCPerf/benchmarks/spark_standalone/spark-2.4.5-bin-hadoop2.7/
433
+
rsync -a benchmarks/spark_standalone/spark-4.0.0-bin-hadoop3/metastore_db root@<target-hostname>:~/DCPerf/benchmarks/spark_standalone/spark-4.0.0-bin-hadoop3/
434
434
```
435
435
436
436
If you do not copy over the `metastore_db` folder, you will see errors like the following
@@ -454,10 +454,10 @@ the better, Spark benchmark also reports `queries_per_hour` which is 3600 divide
454
454
by the execution time. `score` denotes the relative Sparkbench performance to
455
455
DCPerf's baseline.
456
456
For CPU performance analysis, it is
457
-
also helpful to use `execution_time_test_93586-stage-2.0` because Stage 2.0
457
+
also helpful to use `execution_time_test_93586-stage-4.0` because Stage 4.0
458
458
is a compute intensive phase and is much less influenced by I/O. We expect the
459
459
average CPU utilization during the entire benchmark to be around 55~75%. The
460
-
CPU utilization during Stage 2.0 full batch period could reach nearly 100%.
460
+
CPU utilization during Stage 4.0 period could reach nearly 100%.
461
461
462
462
```
463
463
{
@@ -493,8 +493,7 @@ CPU utilization during Stage 2.0 full batch period could reach nearly 100%.
0 commit comments