tree 0e9bd163cf01370c927416764911a495d584e9b2
parent dd362b7b24ea24d8f3c882dab1a69cf78af7cc90
author Willy Tarreau <w@1wt.eu> 1634820328 +0200
committer Willy Tarreau <w@1wt.eu> 1634822904 +0200
encoding latin1

OPTIM: resolvers: move the eb32 node before the data in the answer_item

perf top shows that we spend a lot of time trying to read item->type in
the lookup loop, because the node is placed after the very long name,
so when the node is found, no data is in the cache yet. Let's simply
move the node upper in the struct. This results in the CPU usage of
resolv_validate_dns_response() to drop by 4 points.