This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] Comparing TCP and UDP response times of root name servers
- Previous message (by thread): [dns-wg] Comparing TCP and UDP response times of root name servers
- Next message (by thread): [dns-wg] Comparing TCP and UDP response times of root name servers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Colm MacCárthaigh
colm at stdlib.net
Wed Oct 17 16:50:55 CEST 2012
It might be worth looking at whether the servers support multiple queries over one connection, and whether they support pipelining, and what - if any - difference that makes. A 2nd, and any subsequent, query on a TCP connection won't incur the cost of a handshake, and if pipelining is handled correctly - using Nagling, or TCP_CORK/TCP_NOPUSH, then responses can co-habit TCP packets. I can tell from real-world metrics that at least some resolvers do support, and actually make, multiple requests over the same TCP connection - though they are rare. On Wed, Oct 17, 2012 at 1:49 AM, Anand Buddhdev <anandb at ripe.net> wrote: > [Apologies for duplicates] > > Dear colleagues, > > The RIPE NCC has just published an article on RIPE Labs, comparing the > TCP and UDP response times of DNS queries to the root name servers: > > https://labs.ripe.net/Members/bwijnen/tcp-udp-dns-soa-rt-ratio > > Your comments, questions and suggestions are welcome. > > Regards, > > Anand Buddhdev > RIPE NCC > -- Colm
- Previous message (by thread): [dns-wg] Comparing TCP and UDP response times of root name servers
- Next message (by thread): [dns-wg] Comparing TCP and UDP response times of root name servers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]