Hi guys for those of you that use pi-hole (or similar solutions like adguard home, etc) and wireguard how far away can you be from your wireguard/pi-hole server before latency becomes a major issue?

Also on a side note how many milliseconds of latency would you guys consider to be to slow?

Edit I meant dns latency sorry for not mentioning

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    3 months ago

    As with everything, it depends.

    A video stream and general web browsing can easily take a 300ms delay no issue, but voice and gaming will have issues.

    Voice is fine for upto 150ms according to the IEEE.

      • Bjornir
        link
        fedilink
        English
        arrow-up
        8
        ·
        3 months ago

        Not for the duration of the stream, only for initial page load

        • chaospatterns@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          Yes, but if you hit a company doing DNS based load balancing, DNS is going to return an IP that’s near to your DNS server which may not be near your device. That’s going to add to the latency.

          • canada@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 months ago

            Yeh but assuming you are in the approximate same geo as you pihole it should be the same now if you deploy your pihole across continents then i would say you should really reconsider your decision.

    • just_another_person@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      6
      ·
      edit-2
      3 months ago

      Gotta downvote for misinformation here.

      A requested video stream and web browsing is not bidirectional, and the 300ms you use as an example is not the roundtrip of traffic in that case, but also the response time of the application server.

      The 150ms jitter for real-time voice/video and gaming netcode is streaming bidirectional , and that number is what most users say is not noticeable in real-time communication. You can obviously have more and still have a stable stream up to what the codec will tolerate.