You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the odoh-server creates a new TCP connection for each incoming query to the server(s) defined in the variable nameServers. Even if the connection from the previous query still exists.
Is it planned to implement some kind of connection reuse for performance reasons? Or is the idea to always run it next to a recursive resolver in the same local network, where the time for the tcp handshake can be ignored? But even in this situation, connection reuse could be a good thing.
The text was updated successfully, but these errors were encountered:
Is it planned to implement some kind of connection reuse for performance reasons? Or is the idea to always run it next to a recursive resolver in the same local network, where the time for the tcp handshake can be ignored? But even in this situation, connection reuse could be a good thing.
Yes, this is still planned! We would also welcome PRs, should you have free cycles to spare. :-)
Hello,
I noticed that the odoh-server creates a new TCP connection for each incoming query to the server(s) defined in the variable
nameServers
. Even if the connection from the previous query still exists.Is it planned to implement some kind of connection reuse for performance reasons? Or is the idea to always run it next to a recursive resolver in the same local network, where the time for the tcp handshake can be ignored? But even in this situation, connection reuse could be a good thing.
The text was updated successfully, but these errors were encountered: