Hi,

When updating, my equipment spends nearly as much time "updating
substitutes" as it does downloading substitutes.

The activity is probably exacerbated because I cross-publish substitutes
in my local network.

Would it be more efficient to check whether a particular substitute is
available in an individual query (like DNS) and stop querying for that
substitute after a server was found?

Kind regards
Felix

Reply via email to