Use a real (probing-generated) scorer in benchmarks
authorMatt Corallo <git@bluematt.me>
Sun, 10 Dec 2023 18:23:17 +0000 (18:23 +0000)
committerMatt Corallo <git@bluematt.me>
Thu, 21 Dec 2023 05:35:56 +0000 (05:35 +0000)
commit599042e0489b176b3e5edd770b9a6b79a5ab805b
tree5d5b3a30b29198a7498a1a072ab5c045dbad9797
parentcfafdce2859b8e80541c56f9cd2b3abddbcc479f
Use a real (probing-generated) scorer in benchmarks

Until now, our routing benchmarks used a synthetic scorer,
generated by scoring random paths to build up some history. This is
pretty far removed from real-world routing conditions, as
alternative paths generally have no scoring information and even
the paths we do take have only one or two past scoring results.

Instead, we fetch a static serialized scorer, generated using
minutely probes. This means future changes to the scorer's data may
be harder to benchmark, but makes for substantially more realistic
benchmarks for changes which don't impact the serialized state.
.github/workflows/build.yml
lightning/src/routing/gossip.rs
lightning/src/routing/router.rs
lightning/src/routing/scoring.rs