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

Selfhosted

39435 readers
2 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
40
submitted 4 months ago* (last edited 4 months ago) by [email protected] to c/[email protected]
 

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
[–] [email protected] 8 points 4 months ago (2 children)

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.

[–] [email protected] 2 points 4 months ago (2 children)

Does the 300ms include dns latency?

[–] Bjornir 8 points 4 months ago

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

[–] [email protected] 4 points 4 months ago (1 children)

DNS is only used initially on first load, after that the connection is made via IP and DNS isn't used.

[–] [email protected] 1 points 4 months ago (1 children)

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.

[–] [email protected] 1 points 4 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.

[–] [email protected] -5 points 4 months ago* (last edited 4 months ago) (1 children)

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.

[–] [email protected] 2 points 4 months ago (1 children)

HLS is a bidirectional protocol though - the system's total network latency affects how quickly it can change to a new bitrate stream as conditions improve or degrade. And despite the name, it's not just limited to live content. You can use this to deliver fixed-length content

https://en.wikipedia.org/wiki/HTTP_Live_Streaming

[–] [email protected] -1 points 4 months ago

Automatic downvote.