The LDBC FinBench Driver is a powerful tool designed for benchmarking the performance of graph databases. This is the alpha version of the FinBench driver, currently undergoing alpha testing.
The Driver initiates by reading the configuration file. The file comes pre-filled with configuration data src/main/resources/gradoop/ldbc_finbench_driver_gradoop.properties
.
The driver operates in three modes:
- CREATE_VALIDATION
- VALIDATE_DATABASE
- EXECUTE_BENCHMARK
With CREATE_VALIDATION
mode, you create a database result. validation_parameters_size
denotes the number of results created, while validate_database
refers to the file where the created results are stored.
mode=CREATE_VALIDATION
validation_parameters_size=100
validate_database=validation_params.csv
VALIDATE_DATABASE
mode allows you to verify the SUT. The validate_database
is the result created by CREATE_VALIDATION
mode.
mode=VALIDATE_DATABASE
validate_database=validation_params.csv
Perform the performance test with EXECUTE_BENCHMARK
mode. Here are some crucial configuration parameters that need adjustment when operating the driver:
- thread_count: Represents the number of concurrent requests that the driver can handle, corresponding to the number of active threads running simultaneously within the driver.
- time_compression_ratio: Controls the intensity of the driver's workload. A lower value yields a higher workload in a shorter timeframe.
- ignore_scheduled_start_times: Determines whether the driver should follow the scheduled timings for sending requests. If set to true, the driver sends requests as soon as they are prepared, regardless of the schedule.
- warmup: Denotes the number of preliminary test items processed before the actual benchmarking begins.
- operation_count: Sets the number of test items executed during the actual benchmarking phase after the warm-up.
mode=EXECUTE_BENCHMARK
thread_count=1
time_compression_ratio=0.001
ignore_scheduled_start_times=false
warmup=5
operation_count=10000
To get started, clone the repository and build it with Maven:
mvn clean package -DskipTests
Start the Docker Compose environment located inside /flink
with the pre-bundled SF0.01 dataset:
cd flink
docker-compose build --no-cache
docker-compose up -d
Fill the configuration properties as specified in the comments above the variables. The parameters are pre-set for the bundled dataset.
Then execute the Driver class.
If the run fails before starting, please restart it - the HDFS file system used in the cluster needs some time to start. Oddly, the third run always works :D.
- FinBench Specification: https://github.com/ldbc/ldbc_finbench_docs
- FinBench DataGen: https://github.com/ldbc/ldbc_finbench_datagen
- FinBench Driver: https://github.com/ldbc/ldbc_finbench_driver
- FinBench Transaction Reference Implementation: https://github.com/ldbc/ldbc_finbench_transaction_impls
Please visit these links for further documentation and related resources.