>LADEN // PROJECT DETAILS

PARSING ARCHITECTURE, DIAGRAMS & API ENDPOINTS

>LADEN // LADEN

WEERGAVE INITIALISEREN

Terug naar projecten

Bekijk op GitHub

Voltooidgoneo4jmemgraphtigergraphdocker

Prestatiebenchmark Grafiekdatabases

Benchmarksuite die latentie, geheugen en queryprestaties analyseert tussen graaf- en relationele databases.

Probleem en oplossing

Het kiezen van de juiste database voor complexe sociale netwerken en aanbevelingssystemen.

Functies

Geautomatiseerde benchmarks op verschillende diepteniveaus
Vergelijking van latentiepercentielen (p50, p95, p99)
Gedetailleerde meting van CPU- en geheugengebruik
Reproduceerbare testopstelling met Docker

Technologiestack

Technologie	Versie	Doel	Waarom gekozen
Go	1.25.1	Primary language	Strong concurrency primitives, fast compilation, good driver ecosystem
neo4j-go-driver/v6	v6.2.0	Bolt protocol client for CognoDB, Neo4j, Memgraph	Official driver, supports Bolt 5.x, parameterized queries
go-echarts/v2	v2.7.2	HTML chart generation	Go-native, generates standalone HTML
godotenv	v1.5.1	Environment configuration	Standard .env loading
net/http	stdlib	REST client for TigerGraph	No external dependency needed

Architectuur

Benchmark CLI

Go 1.25.1

Dataset Extractor

Data Loader

Summary Generator

Chart Generator

raw/

SNAP soc-Pokec .gz

processed/

nodes.csv, relationships.csv

results/

JSONL, CSV, HTML

CognoDB Cloud

Bolt 5.x, US-East-4

Neo4j AuraDB

Bolt, US-East-1

Memgraph Cloud

Bolt, US East

TigerGraph Savanna

REST/OpenCypher

Benchmark Engine

Adapter pattern with common GraphDatabase interface (16 methods)
5 database adapters (4 active, FalkorDB disabled due to OOM)
Sequential workload executor with warm-up and measured iterations
Concurrent workload executor with N goroutines and sync.WaitGroup
Factory function for adapter creation from configuration

CLI Pipeline

10 CLI entry points: benchmark, captest, charts, cleanup, dataset, load, runall, summary, verify, verify-load
JSONL append-only result output for crash resilience
CSV summary aggregation with percentile calculation
HTML chart generation via go-echarts
Pipeline automation via runall (verify → load → benchmark → report)

Projectstructuur

cmd

benchmark

captest

charts

cleanup

dataset

load

runall

summary

verify

verify-load

internal

benchmark

concurrent.goConcurrent workload executor

measurement.goMeasurement struct + ResultWriter

runner.goSequential workload executor

safe.goPanic-recovery wrapper

database

cognodb

memgraph

neo4j

tigergraph

types

factory.goDatabase factory/registry

dataset

parser.goCSV node/relationship loader

API-endpoints

Query Workloads (poort 0)

Methode	Route	Doel
Cypher	MATCH (n:Person {id: $id}) RETURN n.id AS id	Point lookup — single node by ID
Cypher	MATCH (n:Person {region: $val}) RETURN n.id AS id LIMIT 10	Indexed lookup — nodes by region
Cypher	MATCH (n:Person {id: $id})-[:FRIEND]->(m:Person) RETURN collect(m.id)	1-hop traversal — direct friends
Cypher	MATCH (n:Person {id: $id})-[:FRIEND]->()-[:FRIEND]->(m:Person) RETURN collect(DISTINCT m.id)	2-hop traversal — friends of friends
Cypher	MATCH (n:Person {id: $id})-[:FRIEND]->()-[:FRIEND]->()-[:FRIEND]->(m:Person) RETURN collect(DISTINCT m.id)	3-hop traversal — extended network
Cypher	MATCH (n:Person) RETURN n.region AS region, count(n) AS cnt ORDER BY cnt DESC LIMIT 10	Aggregation — region distribution
Cypher	CREATE (n:Person {id: $id, region: $region, ...})	Write — create new node

Databaseontwerp

PERSON

5 cols

idPK

string

region

string

gender

string

age

string

completion_percentage

string

FRIEND_EDGE

2 cols

from_id

string

to_id

string

Person (node label)

Kolom	Type	Notities
idPK	STRING	Unique constraint, indexed
region	STRING	Indexed
gender	STRING	Not indexed
age	STRING	Indexed (CognoDB, Neo4j, Memgraph only)
completion_percentage	STRING	Not indexed

49,683 nodes extracted from SNAP soc-Pokec dataset. All properties are strings.

FRIEND (relationship type)

Kolom	Type	Notities
source_id	STRING	Person.id (from)
target_id	STRING	Person.id (to)

100,000 directed relationships. No properties on edges. Many-to-many cardinality.

Directed graph: Person --[FRIEND]--> Person. Many-to-many via graph relationships (no junction table). Relationships are first-class citizens in the graph model.

Belangrijkste ontwerpbeslissingen

Single Bolt Driver for 3 Databases

Beslissing: Use neo4j-go-driver/v6 for CognoDB, Neo4j, and Memgraph

Waarom: All three support Bolt protocol; Cypher is logically equivalent

Voordelen: Code reuse, consistent behavior across databases, adapter pattern isolates DB-specific behavior

Afwegingen: Cannot test database-specific optimizations; Memgraph has its own Go driver

MaxPoolSize = 1

Beslissing: Single connection per benchmark run despite constant defining 10

Waarom: Measure single-connection latency; avoid connection pool effects

Voordelen: Clean latency measurement without pool contention

Afwegingen: Doesn't test connection pooling behavior

JSONL for Raw Results

Beslissing: One JSON object per line, append-only output

Waarom: Stream results without loading all into memory; easy to append across runs

Voordelen: Resilient to crashes (partial results preserved)

Afwegingen: Requires full file scan for aggregation

No Retries on Measured Queries

Beslissing: Zero retries for benchmark queries to capture true latency

Waarom: Network blips and failures are part of real-world performance

Voordelen: Honest performance measurement including failure modes

Afwegingen: Network blips cause false negatives

Goroutine-Per-Client Concurrency

Beslissing: Each concurrent client creates its own database connection

Waarom: Simulates real-world multi-client scenarios; avoids shared connection contention

Voordelen: Realistic concurrency testing with independent connections

Afwegingen: Higher resource usage; connection limits become the bottleneck

MERGE for Idempotent Node Loading

Beslissing: Use MERGE (upsert) instead of CREATE for node loading

Waarom: Makes loading idempotent — running multiple times doesn't create duplicates

Voordelen: Safe re-runs, consistent dataset state

Afwegingen: MERGE is slightly slower than CREATE due to existence checks

Tests

None (no _test.go files)•0 unittests

Wat wordt getest

Capability test matrix (cmd/captest/) — tests all 8 workload types against all databases with small 10-node graph
Connection verification (cmd/verify/) — tests basic connectivity and parameterized queries
Data integrity verification (cmd/verify-load/) — verifies node/relationship counts (49,683 nodes, 100,000 relationships)

Ontbrekende dekking

No unit tests for individual functions (_test.go files do not exist)
No tests for statistical functions (percentile, mean, stddev calculation)
No tests for CSV parsing edge cases (empty datasets, malformed CSVs)
No tests for concurrent behavior
No tests for chart generation correctness
No test framework installed (no testify, gomock)

Belangrijkste uitdagingen

FalkorDB OOM — free tier 100MB RAM limit exceeded by 49K-node dataset, entire adapter disabled
Protocol asymmetry — Bolt (binary) vs REST (HTTP/JSON) confounds direct latency comparison
Resource asymmetry — CognoDB 0.5 vCPU/256MB vs competitors with 2-8x more resources
Free-tier variability — shared resources, auto-pause, time limits affect reproducibility
Ensuring fair comparison across different graph database architectures

Belangrijkste lessen

Adapter pattern for database-agnostic benchmarking with clean interface separation
Goroutine-per-client concurrency model for realistic multi-client simulation
JSONL append-only output for crash-resilient result persistence
Cold-start measurement technique (iteration 0 tagging after warm-up)
Numerical stability in statistical aggregation (percentile calculation)

>LADEN // PROJECT DETAILS

PARSING ARCHITECTURE, DIAGRAMS & API ENDPOINTS

Terug naar projecten

Bekijk op GitHub

Voltooidgoneo4jmemgraphtigergraphdocker

Prestatiebenchmark Grafiekdatabases

Benchmarksuite die latentie, geheugen en queryprestaties analyseert tussen graaf- en relationele databases.

Probleem en oplossing

Het kiezen van de juiste database voor complexe sociale netwerken en aanbevelingssystemen.

Functies

Geautomatiseerde benchmarks op verschillende diepteniveaus
Vergelijking van latentiepercentielen (p50, p95, p99)
Gedetailleerde meting van CPU- en geheugengebruik
Reproduceerbare testopstelling met Docker

Technologiestack

Technologie	Versie	Doel	Waarom gekozen
Go	1.25.1	Primary language	Strong concurrency primitives, fast compilation, good driver ecosystem
neo4j-go-driver/v6	v6.2.0	Bolt protocol client for CognoDB, Neo4j, Memgraph	Official driver, supports Bolt 5.x, parameterized queries
go-echarts/v2	v2.7.2	HTML chart generation	Go-native, generates standalone HTML
godotenv	v1.5.1	Environment configuration	Standard .env loading
net/http	stdlib	REST client for TigerGraph	No external dependency needed

Architectuur

Benchmark CLI

Go 1.25.1

Dataset Extractor

Data Loader

Summary Generator

Chart Generator

raw/

SNAP soc-Pokec .gz

processed/

nodes.csv, relationships.csv

results/

JSONL, CSV, HTML

CognoDB Cloud

Bolt 5.x, US-East-4

Neo4j AuraDB

Bolt, US-East-1

Memgraph Cloud

Bolt, US East

TigerGraph Savanna

REST/OpenCypher

Benchmark Engine

Adapter pattern with common GraphDatabase interface (16 methods)
5 database adapters (4 active, FalkorDB disabled due to OOM)
Sequential workload executor with warm-up and measured iterations
Concurrent workload executor with N goroutines and sync.WaitGroup
Factory function for adapter creation from configuration

CLI Pipeline

10 CLI entry points: benchmark, captest, charts, cleanup, dataset, load, runall, summary, verify, verify-load
JSONL append-only result output for crash resilience
CSV summary aggregation with percentile calculation
HTML chart generation via go-echarts
Pipeline automation via runall (verify → load → benchmark → report)

Projectstructuur

cmd

benchmark

captest

charts

cleanup

dataset

load

runall

summary

verify

verify-load

internal

benchmark

concurrent.goConcurrent workload executor

measurement.goMeasurement struct + ResultWriter

runner.goSequential workload executor

safe.goPanic-recovery wrapper

database

cognodb

memgraph

neo4j

tigergraph

types

factory.goDatabase factory/registry

dataset

parser.goCSV node/relationship loader

API-endpoints

Query Workloads (poort 0)

Methode	Route	Doel
Cypher	MATCH (n:Person {id: $id}) RETURN n.id AS id	Point lookup — single node by ID
Cypher	MATCH (n:Person {region: $val}) RETURN n.id AS id LIMIT 10	Indexed lookup — nodes by region
Cypher	MATCH (n:Person {id: $id})-[:FRIEND]->(m:Person) RETURN collect(m.id)	1-hop traversal — direct friends
Cypher	MATCH (n:Person {id: $id})-[:FRIEND]->()-[:FRIEND]->(m:Person) RETURN collect(DISTINCT m.id)	2-hop traversal — friends of friends
Cypher	MATCH (n:Person {id: $id})-[:FRIEND]->()-[:FRIEND]->()-[:FRIEND]->(m:Person) RETURN collect(DISTINCT m.id)	3-hop traversal — extended network
Cypher	MATCH (n:Person) RETURN n.region AS region, count(n) AS cnt ORDER BY cnt DESC LIMIT 10	Aggregation — region distribution
Cypher	CREATE (n:Person {id: $id, region: $region, ...})	Write — create new node

Databaseontwerp

PERSON

5 cols

idPK

string

region

string

gender

string

age

string

completion_percentage

string

FRIEND_EDGE

2 cols

from_id

string

to_id

string

Person (node label)

Kolom	Type	Notities
idPK	STRING	Unique constraint, indexed
region	STRING	Indexed
gender	STRING	Not indexed
age	STRING	Indexed (CognoDB, Neo4j, Memgraph only)
completion_percentage	STRING	Not indexed

49,683 nodes extracted from SNAP soc-Pokec dataset. All properties are strings.

FRIEND (relationship type)

Kolom	Type	Notities
source_id	STRING	Person.id (from)
target_id	STRING	Person.id (to)

100,000 directed relationships. No properties on edges. Many-to-many cardinality.

Directed graph: Person --[FRIEND]--> Person. Many-to-many via graph relationships (no junction table). Relationships are first-class citizens in the graph model.

Belangrijkste ontwerpbeslissingen

Single Bolt Driver for 3 Databases

Beslissing: Use neo4j-go-driver/v6 for CognoDB, Neo4j, and Memgraph

Waarom: All three support Bolt protocol; Cypher is logically equivalent

Voordelen: Code reuse, consistent behavior across databases, adapter pattern isolates DB-specific behavior

Afwegingen: Cannot test database-specific optimizations; Memgraph has its own Go driver

MaxPoolSize = 1

Beslissing: Single connection per benchmark run despite constant defining 10

Waarom: Measure single-connection latency; avoid connection pool effects

Voordelen: Clean latency measurement without pool contention

Afwegingen: Doesn't test connection pooling behavior

JSONL for Raw Results

Beslissing: One JSON object per line, append-only output

Waarom: Stream results without loading all into memory; easy to append across runs

Voordelen: Resilient to crashes (partial results preserved)

Afwegingen: Requires full file scan for aggregation

No Retries on Measured Queries

Beslissing: Zero retries for benchmark queries to capture true latency

Waarom: Network blips and failures are part of real-world performance

Voordelen: Honest performance measurement including failure modes

Afwegingen: Network blips cause false negatives

Goroutine-Per-Client Concurrency

Beslissing: Each concurrent client creates its own database connection

Waarom: Simulates real-world multi-client scenarios; avoids shared connection contention

Voordelen: Realistic concurrency testing with independent connections

Afwegingen: Higher resource usage; connection limits become the bottleneck

MERGE for Idempotent Node Loading

Beslissing: Use MERGE (upsert) instead of CREATE for node loading

Waarom: Makes loading idempotent — running multiple times doesn't create duplicates

Voordelen: Safe re-runs, consistent dataset state

Afwegingen: MERGE is slightly slower than CREATE due to existence checks

Tests

None (no _test.go files)•0 unittests

Wat wordt getest

Capability test matrix (cmd/captest/) — tests all 8 workload types against all databases with small 10-node graph
Connection verification (cmd/verify/) — tests basic connectivity and parameterized queries
Data integrity verification (cmd/verify-load/) — verifies node/relationship counts (49,683 nodes, 100,000 relationships)

Ontbrekende dekking

No unit tests for individual functions (_test.go files do not exist)
No tests for statistical functions (percentile, mean, stddev calculation)
No tests for CSV parsing edge cases (empty datasets, malformed CSVs)
No tests for concurrent behavior
No tests for chart generation correctness
No test framework installed (no testify, gomock)

Belangrijkste uitdagingen

FalkorDB OOM — free tier 100MB RAM limit exceeded by 49K-node dataset, entire adapter disabled
Protocol asymmetry — Bolt (binary) vs REST (HTTP/JSON) confounds direct latency comparison
Resource asymmetry — CognoDB 0.5 vCPU/256MB vs competitors with 2-8x more resources
Free-tier variability — shared resources, auto-pause, time limits affect reproducibility
Ensuring fair comparison across different graph database architectures

Belangrijkste lessen

Adapter pattern for database-agnostic benchmarking with clean interface separation
Goroutine-per-client concurrency model for realistic multi-client simulation
JSONL append-only output for crash-resilient result persistence
Cold-start measurement technique (iteration 0 tagging after warm-up)
Numerical stability in statistical aggregation (percentile calculation)