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

  • jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    3 months ago

    Depends on your use case there are multiple factors that guide internet use cases

    • Latency - how fast
    • Bandwidth - how wide/much
    • Loss - how much data is lost, or how much data needs to be sent again

    Gaming: latency, loss

    YouTube/movies: bandwidth

    Video chat/voice chat: latency, bandwidth

    Remote desktop/game streaming: latency, bandwidth, loss

    Web browsing: bandwidth, latency

    DNS latency can be a multiplier for browsing the web, a website can include artifacts from other websites, which then can include other websites, which then can include other websites. Each one of those would require another DNS lookup, and round trip time to the website itself etc. however, DNS was architected for local caching, so only the first lookup should be slow, and then afterwards you should keep that DNS information for future lookups so it’s not going to feel too bad once you’ve warmed up the cache

    Rule of thumb: under 100ms feels fine, over starts to feel a little sluggish. Over 300ms and you change your behaviors, and you really feel it.

    • DeemoOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 months ago

      Thanks for the clarification