Add database persistence benchmarks

Benchmark realistic payment and pending-payment persistence workloads
across filesystem, SQLite, and optional PostgreSQL stores. Use the async
KV-store APIs so the measured paths match the database interfaces used by
async persistence.

Author: benthecarman

Cargo.toml

@@ -25,6 +25,7 @@ panic = 'abort'     # Abort on panic
 
 [features]
 default = []
+bench = ["dep:criterion"]
 postgres = ["dep:tokio-postgres", "dep:native-tls", "dep:postgres-native-tls"]
 
 [dependencies]
@@ -77,6 +78,7 @@ uniffi = { version = "0.29.5", features = ["build"], optional = true }
 serde = { version = "1.0.210", default-features = false, features = ["std", "derive"] }
 serde_json = { version = "1.0.128", default-features = false, features = ["std"] }
 log = { version = "0.4.22", default-features = false, features = ["std"]}
+criterion = { version = "0.7.0", features = ["async_tokio"], optional = true }
 
 async-trait = { version = "0.1", default-features = false }
 tokio-postgres = { version = "0.7", default-features = false, features = ["runtime"], optional = true }
@@ -140,6 +142,10 @@ check-cfg = [
 name = "payments"
 harness = false
 
+[[bench]]
+name = "database"
+harness = false
+
 #[patch.crates-io]
 #lightning = { path = "../rust-lightning/lightning" }
 #lightning-types = { path = "../rust-lightning/lightning-types" }

benches/database.rs

@@ -0,0 +1,11 @@
+#[cfg(not(feature = "bench"))]
+compile_error!("run database benchmarks with `cargo bench --features bench --bench database`");
+
+use criterion::{criterion_group, criterion_main, Criterion};
+
+fn database_benchmark(c: &mut Criterion) {
+	ldk_node::bench::database_benchmark(c);
+}
+
+criterion_group!(benches, database_benchmark);
+criterion_main!(benches);