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>
Tue, 12 Dec 2023 04:28:35 +0000 (04:28 +0000)
commitc98e3f750349ca2c8037ecfdbcb3935f94044011
treedf80c1b0d2f95599780c397596907ddb3fa994eb
parent2884b00c96087fdf49d309aaee61ee2c8e567ff0
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