Pathvector relies on external datasources to generate configuration, such as PeeringDB, IRR databases, and the RPKI. There are various mechanisms to cache this data to decrease latency and reduce load on these external services.
Pathvector has an internal PeeringDB cache that stores PeeringDB objects for the duration of a single
pathvector generate run. This does not cache for longer than a single command invocation.