Benchmark configuration
Benchmarks require a dedicated configuration file pointing to test databases. This isolates benchmark runs from production data.
Configuration file
Section titled “Configuration file”The benchmark uses a standard Meta config YAML with test-specific values. A reference config is provided at oc_meta/run/benchmark/benchmark_config.yaml.
Required settings
Section titled “Required settings”# Test triplestore endpointstriplestore_url: http://127.0.0.1:8805/sparqlprovenance_triplestore_url: http://127.0.0.1:8806/sparql
# Benchmark directoriesinput_csv_dir: oc_meta/run/benchmark/inputbase_output_dir: oc_meta/run/benchmark/outputoutput_rdf_dir: oc_meta/run/benchmark/output/
# Test Redis (separate from production)redis_host: localhostredis_port: 6381redis_db: 10cache_db: 11Test databases
Section titled “Test databases”Start the test databases before running benchmarks:
./test/start-test-databases.shThis starts:
- Virtuoso (data): port 8805
- Virtuoso (provenance): port 8806
- Redis: port 6381
Cleanup
Section titled “Cleanup”By default, the benchmark resets all test databases after each run:
- Virtuoso:
RDF_GLOBAL_RESET()via Docker exec - Redis:
FLUSHDBon counter and cache databases - Output files: deleted
Use --no-cleanup to preserve data for inspection.