#Conversations_im is doing pretty extensive DNS caching.
-
#Conversations_im is doing pretty extensive DNS caching. If you set the TTL of your DNS records relatively high (86400 seconds for example) Conversations can avoid some round trips during connect. Another round trip can be avoided if you prioritize the _xmpps-client SRV entry. This can significantly improve the performance in rough networking environments.
In good networks we can establish a full connection in under 500ms.
-
#Conversations_im is doing pretty extensive DNS caching. If you set the TTL of your DNS records relatively high (86400 seconds for example) Conversations can avoid some round trips during connect. Another round trip can be avoided if you prioritize the _xmpps-client SRV entry. This can significantly improve the performance in rough networking environments.
In good networks we can establish a full connection in under 500ms.
Do you foresee issue in home hosting scenarios?
In that case we have a dynamip IP and a local DNS override (meaning in wifi, ther server dns is a local ip and from 5g it's a public ip)
-
Do you foresee issue in home hosting scenarios?
In that case we have a dynamip IP and a local DNS override (meaning in wifi, ther server dns is a local ip and from 5g it's a public ip)
@tuxicoman Caching is done on a per-network basis (or per DNS server, technically). So on your LAN it should be hitting a different cache than on 5G.