Olaoluwa Osuntokun 57872b9cff discovery: make gossip filter semaphore capacity configurable ...

In this commit, we make the gossip filter semaphore capacity configurable
through a new FilterConcurrency field. This change allows node operators
to tune the number of concurrent gossip filter applications based on
their node's resources and network position.

The previous hard-coded limit of 5 concurrent filter applications could
become a bottleneck when multiple peers attempt to synchronize
simultaneously. By making this value configurable via the new
gossip.filter-concurrency option, operators can increase this limit
for better performance on well-resourced nodes or maintain conservative
values on resource-constrained systems.

We keep the default value at 5 to maintain backward compatibility and
avoid unexpected resource usage increases for existing deployments. The
sample configuration file is updated to document this new option.

2025-08-06 11:34:42 +02:00

..

address_test.go

…

address.go

…

autopilot.go

…

bitcoind.go

…

btcd.go

…

caches.go

…

chain.go

…

cluster.go

…

color_test.go

…

color.go

…

config.go

…

db_test.go

…

db.go

…

dev_integration.go

…

dev.go

…

error.go

…

fee.go

…

gossip.go

…

healthcheck.go

…

htlcswitch.go

…

interface.go

…

invoices.go

…

log.go

…

monitoring_off.go

…

monitoring_on.go

…

neutrino.go

…

pprof.go

…

protocol_experimental_off.go

…

protocol_experimental_on.go

…

protocol_integration.go

…

protocol_legacy_off.go

…

protocol_legacy_on.go

…

protocol.go

…

remotesigner.go

…

routing.go

…

rpcmiddleware.go

…

sweeper.go

…

tor.go

…

watchtower.go

…

workers_test.go

…

workers.go

…

wtclient.go

…