-
Notifications
You must be signed in to change notification settings - Fork 0
MADlib Benchmark Requirements
In order to well understand and be able to improve the performance of MADlib modules we need a proper benchmark framework. The purpose of this document is to lay out requirements for such a solution.
The main goals for MADlib benchmarks are:
-
Competitive comparison
Our initial comparison targets should be R and Mahout, as it should be easy to setup corresponding tests on the same HW configuration. Initial testing could be performed on a single host.
-
Regression tests
We should keep a log book of current run-times and rerun the appropriate tests after any substantial modifications to existing modules. The summary of it should be available on the wiki.
-
Profiling & optimization
MADlib benchmarks could potentially be very useful during ad-hoc profiling and optimization. Although it does not need to reinvent the performance metrics collection, as there are already tools for that.
The following algorithms should be tested. Reference links to R and Mahout libraries are given below:
- Naive-Bayes Classification: [[R|http://finzi.psych.upenn.edu/R/library/e1071/html/naiveBayes.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/bayesian.html]]
- Linear Regression: [[R|http://finzi.psych.upenn.edu/R/library/fRegression/html/regFit.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/locally-weighted-linear-regression.html]]
- Logistic Regression: [[R|http://finzi.psych.upenn.edu/R/library/rms/html/lrm.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/logistic-regression.html]]
- Decision Trees: [[R|http://finzi.psych.upenn.edu/R/library/RWeka/html/Weka_classifier_trees.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/random-forests.html]]
- Support Vector Machines: [[R|http://finzi.psych.upenn.edu/R/library/kernlab/html/ksvm.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/support-vector-machines.html]]
- Association Rules: [[R|http://finzi.psych.upenn.edu/R/library/arules/html/00Index.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/parallel-frequent-pattern-mining.html]]
- k-means Clustering: [[R|http://finzi.psych.upenn.edu/R/library/stats/html/kmeans.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/k-means-clustering.html]]
- SVD Matrix Factorisation: [[R|http://finzi.psych.upenn.edu/R/library/corpcor/html/fast.svd.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/dimensional-reduction.html]]
- Latent Dirichlet Allocation: [[R|http://finzi.psych.upenn.edu/R/library/topicmodels/html/lda.html]], [[Mahout|https://cwiki.apache.org/MAHOUT/latent-dirichlet-allocation.html]]
In order to fulfill the above goals the MADlib benchmark tool should possess the following characteristics:
-
Portability
It must run on all OS and DB platforms supported by MADlib.
-
Scalability
It should be easy to scale the data size for a predefined test.
-
Repetitiveness
It should be possible to rerun the performance test with identical starting conditions. This applies to both the data generation as well as the execution phase.
-
Modularity
It should be easy to add new performance tests for new or existing modules.
-
Automation
Execution of the benchmark (full or per module) should be easy to automate. Ideally this utility should be controlled from by single executable.
#
# Table definition
#
- table:
name : my_table # table name
distby : col_1 # column name for distributed by clause
#
# Column definition
#
- colname : col1
datatype : text|integer|float|boolean
values :
type : pk|list|random|fk
#
# Types explained:
#
# pk - primary key, unique sequence of integers generated
# using a sequence. No additional config needed.
# list - list of values with frequency weights assigned
# each value will be drawn with probability of:
# weight/sum(all_weights)
# random - random number from a selected prob. distribution
# with specified seed and distribution parameters
# fk - randomly selected values from another table.column
#
list :
- value : val_1
weight: 1
- value : val_2
weight: 3
...
random : normal, chi-square, poisson, etc.
seed : random|constant
parameters : x,y,z,...
fk : some_other_table.some_column
... For each MADlib module performance test one should be able to define (possibly in a common config file):
- Input Definition
- Run-time call arguments
Both data generation and test execution should be timed and all information should be saved in a database table located in MADlib schema, e.g.:
TABLE madlib.benchmark (
module TEXT
(runtime_args)
(input_defintion)
dgen_start TIMESTAMP
dgen_end TIMESTAMP
exec_start TIMESTAMP
exec_end TIMESTAMP
)
-
Because the benchmark tool requires connection to a database with MADlib extensions installed it is possible to think of it as an extension to madpack - the MADlib installer.