Skip to content

Commit ffd836c

Browse files
authored
Merge pull request #37 from Alexsandruss/dev/knn-extension
kNN bench, configs and runner update
2 parents 296a991 + 1c72cd5 commit ffd836c

16 files changed

+1850
-146
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,5 +10,6 @@ __work*
1010

1111
# Datasets
1212
dataset
13+
data
1314
*.csv
1415
*.npy

README.md

100644100755
Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ See benchmark results [here](https://intelpython.github.io/scikit-learn_bench).
1010

1111
* [Prerequisites](#prerequisites)
1212
* [How to create conda environment for benchmarking](#how-to-create-conda-environment-for-benchmarking)
13+
* [How to enable daal4py patching for scikit-learn benchmarks](#how-to-enable-daal4py-patching-for-scikit-learn-benchmarks)
1314
* [Running Python benchmarks with runner script](#running-python-benchmarks-with-runner-script)
1415
* [Supported algorithms](#supported-algorithms)
1516
* [Algorithms parameters](#algorithms-parameters)
@@ -30,13 +31,15 @@ Create a suitable conda environment for each framework to test. Each item in the
3031
* [**cuml**](https://github.com/PivovarA/scikit-learn_bench/blob/master/cuml/README.md#how-to-create-conda-environment-for-benchmarking)
3132
* [**xgboost**](https://github.com/PivovarA/scikit-learn_bench/tree/master/xgboost/README.md#how-to-create-conda-environment-for-benchmarking)
3233

34+
## How to enable daal4py patching for scikit-learn benchmarks
35+
Set specific environment variable `export FORCE_DAAL4PY_SKLEARN=YES`
3336

3437
## Running Python benchmarks with runner script
3538

36-
Run `python runner.py --config configs/config_example.json [--output-format json --verbose]` to launch benchmarks.
39+
Run `python runner.py --configs configs/config_example.json [--output-format json --verbose]` to launch benchmarks.
3740

3841
runner options:
39-
* ``config`` : the path to configuration file
42+
* ``configs`` : configuration files paths
4043
* ``dummy-run`` : run configuration parser and datasets generation without benchmarks running
4144
* ``verbose`` : print additional information during benchmarks running
4245
* ``output-format``: *json* or *csv*. Output type of benchmarks to use with their runner

0 commit comments

Comments
 (0)