Login
You're viewing the functional.cafe public feed.
  • Nov 17, 2026, 9:27 PM

    With systemd-resolve it will submit its queries through systemd-resolve's varlink API directly using non-blocking API calls.

    Without, it falls back to terrible synchronous POSIX APIs.

    💬 1🔄 0⭐ 0

Replies

  • Nov 17, 2026, 9:28 PM

    The main idea being that of course we have to resolve a whole bunch of host names and currently we do a SRV first, then address and it's ... slow.

    With a parallel resolver we can resolve SRV records, A, AAAA all in parallel.

    Resolving a SRV record to a bunch of hosts queues A/AAAA for those hosts as well, and the outcome is a flat list of hosts you can connect to

    💬 1🔄 0⭐ 0
  • Nov 17, 2026, 9:33 PM

    One thought behind this is it allows us to probe multiple mirrors in parallel, connect to them in parallel and then connect to the fastest replying ones.

    (TLS handshakes not included in the connection RTT prober)

    💬 1🔄 0⭐ 0
  • Nov 17, 2026, 9:34 PM

    Now when I say in parallel I am lying because we would institute say a 30 ms time out for each IP and then get the next one from the resolver list and add it to the IPs we are probing in happy eyeballs fashion.

    💬 0🔄 0⭐ 0