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
    8
    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.

    • just_another_person@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      5
      ·
      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.

  • jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    4
    ·
    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.

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    3 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    DNS Domain Name Service/System
    HTTP Hypertext Transfer Protocol, the Web
    IP Internet Protocol
    PiHole Network-wide ad-blocker (DNS sinkhole)
    VPN Virtual Private Network

    5 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

    [Thread #914 for this sub, first seen 9th Aug 2024, 13:05] [FAQ] [Full list] [Contact] [Source code]