[Unbound-users] concurrent processing of queries from the same TCP connection

W.C.A. Wijngaards wouter at nlnetlabs.nl
Mon Jan 6 10:09:46 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Zi,

On 12/18/2013 02:31 AM, Zi Hu wrote:
> Hi,
> 
> I noticed that when unbound processes queries from the same TCP 
> connection, it processes them sequentially.

Yes.

> If I send multiple queries over the same TCP connection, unbound 
> processes them one by one (not concurrently), which causes head of
> line blocking: The later queries have to wait previous queries to
> get processed.
> 
> The question is: Is there any particular reason that unbound
> doesn't support concurrent processing of queries from the same TCP
> connection?

The reason is a lot of code for little gain.  Concurrent processing
(although possible because queries from different connections get
concurrent processing already) is likely to be a lot of code to implement.

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSyoDqAAoJEJ9vHC1+BF+N8OgP/RvH5V/p3bcduN8vqo5JtFe5
MYFcNNdh5lqG28SwrDysFpBxZJqNGzxIVnSq2rDYvWsHgUjq6BBL9BS2Pe8hUHdr
HBsrTDLLBdoMbe9BS98Qs2uLb+uqhzu0Jh87EVcjQ3luduoWWmR0v29s5U95bmgY
AK8pwjEhwY05z0tWQYGuSCXKJA0oLSXgq5Ukv790jP4mPXXVtIrNPqxx9n93H36I
c7ST2UZ3w4Z7KeEmkHhRBXyRdlIeYp80WEmO20eeb5um1SebBVWATlnGUnOQIpaa
bTEKF+K+qNVWju0g+Cjp8heSyUPrlfa1VHjpXcYvowEyxV9t15QlmP1LVB3t0mPq
IyD6VQ7nMV9moRChEN2QuYmTsajIH2G+ZJirAIJQS0F103E4mNXQCMbeGJEk6f1U
lgEEDPggeAxTvemSCZoaQTA/InYXcVYgvMu8Tz2Z+rihttfEHKb3/SwJuPZfA2AW
KzzOxlIaTWXqEdQRNRLiHjHgC9/OSCczv/I9gOXIUr49zVPwLL7qctDj1igzI1O6
JbFVxphJrX+lisXzPlyedQknnnHLfEs2B1+wuLtE05YEy+lF+KtBN634FO0MEcWd
Q0RkDvQTIa9/iuv6PfrjUfo9Y4NCSSi9ujWm6+N5ldrZu7TLvqf4QML7yx4dY3us
fcA+sMCtdijXKhqgckOv
=+JSW
-----END PGP SIGNATURE-----



More information about the Unbound-users mailing list