The explosion of human-generated information necessitates automated analytical processing to cluster, classify, and filter this information. Recommender systems are a subclass of information filtering systems that seek to predict the 'rating' or 'preference' that a user would give to an item. They have become extremely popular in recent years and are applied in various applications like movies, music, news, books, research articles, search queries, and social tags. Because these applications suffer from I/O operations, most are running in memory nowadays to provide realtime results.
This benchmark uses Apache Spark and runs a collaborative filtering algorithm (alternating least squares, ALS) provided by Spark MLlib in memory on a dataset of user-movie ratings. The metric of interest is the time in seconds for computing movie recommendations.
Supported tags and their respective Dockerfile tags:
latestcontains the algorithm and application entrypoint.
The benchmark uses user-movie ratings datasets provided by Movielens. Run the following command to create the dataset container:
$ docker create --name movielens-data cloudsuite/movielens-datasetMore information about the dataset is available at cloudsuite/movielens-dataset.
The benchmark runs the ALS algorithm on Spark through the spark-submit script distributed with Spark. It takes two arguments: the dataset for training and the personal ratings file for recommendations. We provide two training datasets (one small and one large) and a sample personal ratings file.
To run the benchmark with the small dataset and the provided personal ratings file:
$ docker run --volumes-from movielens-data cloudsuite/in-memory-analytics \
/data/ml-latest-small /data/myratings.csvAny additional arguments are passed to spark-submit, which is the interface to submit jobs to Spark.
Any arguments after the two mandatory ones are passed to spark-submit and are used to tweak execution parameters. For example, to ensure that Spark has enough memory allocated to be able to execute the benchmark in memory, supply it with --driver-memory and --executor-memory arguments:
$ docker run --volumes-from movielens-data cloudsuite/in-memory-analytics \
/data/ml-latest /data/myratings.csv \
--driver-memory 4g --executor-memory 4gThis section explains how to run the benchmark using multiple Spark workers (each running in a Docker container) that can be spread across multiple nodes in a cluster.
First, create a dataset image on every physical node where Spark workers will be running.
$ docker create --name movielens-data cloudsuite/movielens-datasetStart Spark master and Spark workers. You can start the master node with the following command:
$ docker run -dP --net host --name spark-master \
cloudsuite/spark:3.3.2 masterBy default, the container uses the hostname as the listening IP for the connections to the worker nodes. Ensure all worker machines can access the master machine using the master hostname if the listening IP is kept by default. You can also override the listening address by setting the environment variable SPARK_MASTER_IP with the container option -e SPARK_MASTER_IP=X.X.X.X.
The workers get access to the datasets with --volumes-from movielens-data.
# Set up worker1
$ docker run -dP --net host --volumes-from movielens-data --name spark-worker-01 \
cloudsuite/spark:3.3.2 worker spark:https://SPARK-MASTER:7077
# Setup worker 2
$ docker run -dP --net host --volumes-from movielens-data --name spark-worker-02 \
cloudsuite/spark:3.3.2 worker spark:https://SPARK-MASTER:7077
# ...SPARK_MASTER is Spark master's listening address.
Finally, run the benchmark as the client to activate the Spark master:
$ docker run --rm --net host --volumes-from movielens-data \
cloudsuite/in-memory-analytics \
/data/ml-latest-small /data/myratings.csv \
--driver-memory 4g --executor-memory 4g \
--master spark:https://SPARK-MASTER:7077