40
Latency with pi-hole + wireguard (docs.pi-hole.net)
submitted 3 months ago* (last edited 3 months ago) by Deemo@bookwormstory.social to c/selfhosted@lemmy.world
25 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments
[-] jet@hackertalks.com 6 points 3 months ago* (last edited 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.

[-] Deemo@bookwormstory.social 2 points 3 months ago

Thanks for the clarification

this post was submitted on 09 Aug 2024
40 points (100.0% liked)

Selfhosted

40406 readers
493 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz